From: Alexander Viro <viro@math.psu.edu>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Richard Gooch <rgooch@ras.ucalgary.ca>,
linux-kernel@vger.kernel.org,
devfs-announce-list@vindaloo.ras.ucalgary.ca
Subject: Re: [PATCH] New devfs core
Date: Mon, 5 Nov 2001 14:51:48 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.21.0111051447060.24894-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111051742231.27028-100000@duckman.distro.conectiva>
On Mon, 5 Nov 2001, Rik van Riel wrote:
> On Mon, 5 Nov 2001, Richard Gooch wrote:
>
> > But since interest has been expressed ;-) in seeing this code, here it
> > is. So don't flame if you see problems. Remember that this is a very
> > rough cut. I have a list of "issues" to process before I consider this
> > alpha quality.
>
> This is nice for 2.5, but I have to wonder what you're
> going to do in order to get the bugs in 2.4 devfs fixed.
Come on. Regardless of the quality of new code (I hadn't looked at the
patched tree yet, but from the look at patch itself locking is heavily
overdone, so my gut feeling is that there are deadlocks), it's no worse
than the old one.
I.e. as long as it doesn't touch the rest of tree, situation hadn't
become worse. Usual arguments re lost testing obviously do not apply -
replaced code is known to be broken _and_ impossible to fix without a
massive rewrite. So all old testing had been worthless anyway.
next prev parent reply other threads:[~2001-11-05 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 19:31 [PATCH] New devfs core Richard Gooch
2001-11-05 19:44 ` Rik van Riel
2001-11-05 19:51 ` Alexander Viro [this message]
2001-11-05 20:03 ` Richard Gooch
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=Pine.GSO.4.21.0111051447060.24894-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=devfs-announce-list@vindaloo.ras.ucalgary.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--cc=riel@conectiva.com.br \
/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;
as well as URLs for NNTP newsgroup(s).