9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] rb kernel issue
Date: Tue,  5 Nov 2013 14:17:09 -0500	[thread overview]
Message-ID: <c4247651917d82ac9bc32f772422171f@mikro> (raw)
In-Reply-To: <117b4d1db2043054bf1dd9a2abe7e410@gmx.de>

On Tue Nov  5 13:06:06 EST 2013, cinap_lenrek@gmx.de wrote:
> how is this possible? execing a zero byte file should fail
> header parsing, which is portable code in sysexec(). can
> you reproduce the panic?
>
> i get this on a pc:
>
> term% ./xxx
> ./xxx: exec header invalid

this is not what happened.  what happened was
/sys/src/cmd/vl/v.out was a valid mips executable.
unfortuntely, vl creates/truncates (i haven't looked yet)
v.out  but when the name of vl is actually v.out,
the process nukes its own text.  so the next page fault in text/data
should be unfixable.  this should terminate the running
process, not panic the kernel.

- erik



      reply	other threads:[~2013-11-05 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 17:43 erik quanstrom
2013-11-05 18:58 ` cinap_lenrek
2013-11-05 19:17   ` erik quanstrom [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c4247651917d82ac9bc32f772422171f@mikro \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).