From: David Konerding <dek_ml@konerding.com>
To: unlisted-recipients:; (no To-header on input)@localhost
Cc: linux-kernel@vger.kernel.org
Subject: Re: "mount -o loop" lockup issue
Date: Tue, 27 Mar 2001 00:32:36 -0800 [thread overview]
Message-ID: <3AC05024.747A2AD6@konerding.com> (raw)
In-Reply-To: <E14hkwq-0002y0-00@the-village.bc.nu>
Alan Cox wrote:
> > It's a bug in Linux 2.4.2, fixed in later versions. Regression/quality control
> > testing would
> > have caught this, but the developers usually just break things and wait for people
> > to complain
> > as their "Regression" testers.
>
> Hardly. We knew it was broken since well before 2.4.0. It just got a little
> interesting to fix.
And this is described in what release notes? It worked just fine on Red Hat 7.0's 2.4
kernel.... oh wait, I see that they fixed it before they released it.
next prev parent reply other threads:[~2001-03-27 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 1:56 "mount -o loop" lockup issue David E. Weekly
2001-03-27 3:31 ` Jason Madden
2001-03-27 3:50 ` David Konerding
2001-03-27 4:19 ` Alan Cox
2001-03-27 8:32 ` David Konerding [this message]
2001-03-27 13:24 ` Mohammad A. Haque
2001-03-27 18:51 ` J Sloan
2001-03-27 19:33 ` Alexander Viro
2001-03-27 5:30 ` Rik van Riel
2001-03-27 8:13 ` David Konerding
2001-03-27 12:31 ` Rik van Riel
2001-03-27 13:51 ` Kernel QA James Lewis Nance
2001-03-27 18:02 ` Shawn Starr
2001-03-27 22:09 ` Alexander Valys
2001-03-27 16:25 ` "mount -o loop" lockup issue Alan Cox
2001-03-27 3:50 ` Mohammad A. Haque
2001-03-27 3:59 ` William Stearns
-- strict thread matches above, loose matches on Subject: below --
2001-03-27 19:25 Joerg Pommnitz
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=3AC05024.747A2AD6@konerding.com \
--to=dek_ml@konerding.com \
--cc=linux-kernel@vger.kernel.org \
/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