mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: "Giacomo A. Catenazzi" <cate@dplanet.ch>
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: OOPS[devfs]: reproducible in vfs_follow_link 2.4.9,2.4.10-pre4
Date: Fri, 7 Sep 2001 13:33:51 -0600	[thread overview]
Message-ID: <200109071933.f87JXp913517@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <3B993207.787B0D5@dplanet.ch>
In-Reply-To: <3B97744E.7020007@dplanet.ch> <Pine.GSO.4.21.0109061454480.7097-100000@weyl.math.psu.edu> <200109061941.f86Jfak01921@vindaloo.ras.ucalgary.ca> <3B993207.787B0D5@dplanet.ch>

Giacomo A. Catenazzi writes:
> Richard Gooch wrote:
> > 
> > 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.
[I said it was fixed for UP in recent devfs patches]
> > 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.
> 
> No, your patch  didn't work.
> I have still the oops.

Hm! Is this a UP or SMP kernel?

> I investigates, and the oops come in the mountall script (in init.d),
> when running: mount -avt nonfs,nosmbfs.
> (I noticed thet at this point kernel load floppy modules, but when I
> removed also the floppy module, the oops reappers.)

Hm. I've had one other bug report which initially seemed to be
devfs-related, but it was also related to the floppy driver as
well. IIRC, elsewhere Alan noted there seemed to be some problems with
the floppy driver. I suspect the bug you (and the other person) are
having is related to the floppy driver and not devfs.

Please try renaming/removing your floppy driver and see if the problem
persists. I bet it goes away. As Al mused, it was odd that the problem
only appears now. While there are known races in devfs, no-one has
ever encountered these in real life (targetted exploits are not "real
life"). So I too am surprised that suddenly there appears a problem
with devfs.

In the meantime, my tree is getting closer to the stage where I will
attempt a compile. Soon I will be able to dispel this dark cloud of
"devfs races" that Al keeps muttering about :-)

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2001-09-07 19:34 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   ` OOPS[devfs]: " Richard Gooch
2001-09-07 19:33     ` Richard Gooch [this message]
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=200109071933.f87JXp913517@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®