From: Gerd Knorr <kraxel@bytesex.org>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] [patch] mconsole_proc rewrite (and crash fix).
Date: Fri, 20 Aug 2004 13:08:17 +0200 [thread overview]
Message-ID: <20040820110817.GA21170@bytesex> (raw)
In-Reply-To: <200408111957.40575.blaisorblade_spam@yahoo.it>
On Wed, Aug 11, 2004 at 07:57:40PM +0200, BlaisorBlade wrote:
^^^^^^
Did the mail really travel that long, or is your clock broken?
> Actually the exec command cannot send anything to the mconsole, but since it
> invokes sh -c it allows for redirections to new consoles.
Having the output go directly to mconsole is much easier to handle
through.
> > The old code had the problem that the kernel crashed after calling
> > "uml_mconsole proc <somefile>" a few times. I havn't tracked what
> > exactly causes the problem, I guess trying to access the procfs without
> > actually mounting it somewhere causes some corruption of kernel data
> > structures.
>
> Who said that he didn't have mounted /proc inside the guest?
Code looks like that, as it uses get_filesystem and all that instead of
doing a simple /proc/... path lookup. What is the point of doing it
that way, other than make it work even if procfs is not mounted below
/proc?
> However, I see basically two bugs:
> 1) why put_filesystem is not called at the end?
It is called earlier, right after ->get_sb() call. Which looks sane to
me, as a successfull get_sb() should increase the refcount and thus
releasing the filesystems afterwards should be safe. I'm no VFS expert
through.
Gerd
--
return -ENOSIG;
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-08-20 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 20:40 [uml-devel] [patch] mconsole_proc rewrite (and crash fix) Gerd Knorr
2004-08-11 17:57 ` BlaisorBlade
2004-08-20 11:08 ` Gerd Knorr [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=20040820110817.GA21170@bytesex \
--to=kraxel@bytesex.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.