From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Alexander Viro <viro@math.psu.edu>
Cc: Giacomo Catenazzi <cate@dplanet.ch>, linux-kernel@vger.kernel.org
Subject: Re: OOPS[devfs]: reproducible in vfs_follow_link 2.4.9,2.4.10-pre4
Date: Thu, 6 Sep 2001 13:41:36 -0600 [thread overview]
Message-ID: <200109061941.f86Jfak01921@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.GSO.4.21.0109061454480.7097-100000@weyl.math.psu.edu>
In-Reply-To: <3B97744E.7020007@dplanet.ch> <Pine.GSO.4.21.0109061454480.7097-100000@weyl.math.psu.edu>
Alexander Viro writes:
>
>
> On Thu, 6 Sep 2001, Giacomo Catenazzi wrote:
>
> > Hello.
> >
> > Since yesterdey, every time I run a 2.4.9 or 2.4.10pre-4 without the
> > "devfs=nomount" I
> > have two oops + /usr, /home /boot not mounted (all (also /): ext2).
>
> Don't use devfs. One of the known bugs - devfs passes a string
> to vfs_follow_link() and doesn't care to preserve it until
> vfs_follow_link() is done.
Devfs-patch-v186 had my first fix for this. It removes the race on UP
entirely, and has only a small SMP race. So apply the latest devfs
patch:
ftp://ftp.kernel.org/pub/linux/kernel/people/rgooch/v2.4/devfs-patch-current.gz
It was released early August.
> E.g. rmmod during the symlink traversal will end up with
Was an rmmod being performed at this time?
> And yes, Richard had been informed about that months ago. Sigh...
And my first patch was a month ago. And I've been fixing other races
and doing code cleanups as well. I've been sending Linus my patches
for a month now, but he hasn't applied them. Sigh...
And my current tree has half the code ripped apart as I add
refcounting and spinlocks to key places, and do proper freeing upon
unregister. My apologies for not posting it to the list, but it
doesn't compile yet, and won't for a while.
If people could test the latest devfs patch, that would be really
helpful. Linus isn't applying it because he's concerned that the many
SD support may break something. Even if you don't have many SD's,
please apply the patch and send a message to the list (and Cc: me)
stating whether or not your system still works.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-09-06 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 20:45 Giacomo A. Catenazzi
2001-09-06 13:04 ` OOPS: " Giacomo Catenazzi
2001-09-06 19:10 ` Alexander Viro
2001-09-06 19:41 ` Richard Gooch [this message]
2001-09-07 19:33 ` OOPS[devfs]: " Richard Gooch
2001-09-10 7:59 Giacomo Catenazzi
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=200109061941.f86Jfak01921@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=cate@dplanet.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®