[lkml]   [2001]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: OOPS[devfs]: reproducible in vfs_follow_link 2.4.9,2.4.10-pre4
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

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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:02    [W:0.035 / U:0.712 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site