From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Alexander Viro <viro@math.psu.edu>
Cc: Pierre Rousselet <pierre.rousselet@wanadoo.fr>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Keith Owens <kaos@ocs.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.1-pre5 not easy to boot with devfs
Date: Sun, 2 Dec 2001 10:55:43 -0700 [thread overview]
Message-ID: <200112021755.fB2Hthl10340@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.GSO.4.21.0112021150310.12801-100000@binet.math.psu.edu>
In-Reply-To: <3C0A025C.88B7A2C3@wanadoo.fr> <Pine.GSO.4.21.0112021150310.12801-100000@binet.math.psu.edu>
Alexander Viro writes:
>
>
> On Sun, 2 Dec 2001, Pierre Rousselet wrote:
>
> > Here is the final (i hope) verdict of my devfs testbox :
> >
> > 2.4.16 with devfsd-1.3.18/1.3.20 : OK
> > 2.4.17-pre1 " : Broken
> > 2.5.1-pre1 " : OK
> > 2.5.1-pre2 with or without v200 : Broken
> > 2.5.1-pre5 " : Broken
>
> IOW, merge of new devfs code (2.4.17-pre1 in -STABLE, 2.5.1-pre2 in -CURRENT).
>
> We really need CONFIG_DEBUG_* forced if CONFIG_DEVFS_FS is set. Otherwise
> we'll be getting tons of bug reports due to silent memory corruption.
>
> Keith, is there a decent way to do that? For 2.4.17 it would help a
> lot...
Is that worth the effort? Hopefully by 2.4.17-rc I'll have fixed the
bug, so it won't be an issue.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-12-02 17:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 4:43 Pierre Rousselet
2001-12-01 5:01 ` Alexander Viro
2001-12-01 5:37 ` Linus Torvalds
2001-12-01 7:01 ` Richard Gooch
2001-12-01 8:45 ` Pierre Rousselet
2001-12-02 19:40 ` Bongani Hlope
2001-12-01 9:59 ` Pierre Rousselet
2001-12-01 18:36 ` Richard Gooch
2001-12-01 20:37 ` Pierre Rousselet
2001-12-01 23:20 ` Richard Gooch
2001-12-02 1:11 ` Pierre Rousselet
2001-12-02 10:28 ` Pierre Rousselet
2001-12-02 16:59 ` Alexander Viro
2001-12-02 17:14 ` Alan Cox
2001-12-02 18:02 ` Richard Gooch
2001-12-03 12:58 ` Jens Axboe
2001-12-03 19:06 ` Richard Gooch
2001-12-03 20:52 ` Jens Axboe
2001-12-02 22:57 ` Keith Owens
2001-12-03 4:50 ` Pierre Rousselet
2001-12-02 17:55 ` Richard Gooch [this message]
2001-12-03 19:54 ` Alexander Viro
2001-12-02 8:05 ` Pierre Rousselet
2001-12-01 23:47 ` Richard Gooch
2001-12-02 7:11 ` Pierre Rousselet
2001-12-02 21:22 ` Richard Gooch
2001-12-02 9:27 ` Pierre Rousselet
2001-12-03 6:33 ` Richard Gooch
2001-12-03 5:57 ` Pierre ROUSSELET
2001-12-03 12:16 ` Pierre Rousselet
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=200112021755.fB2Hthl10340@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=pierre.rousselet@wanadoo.fr \
--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®