From: Jens Axboe <axboe@suse.de>
To: Mark Bratcher <mbratche@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.0 loop device still hangs
Date: Sun, 28 Jan 2001 03:43:00 +0100 [thread overview]
Message-ID: <20010128034300.A32375@suse.de> (raw)
In-Reply-To: <3A70EF20.1B02B307@rochester.rr.com> <3A72E8C7.138BB69E@rochester.rr.com>
In-Reply-To: <3A72E8C7.138BB69E@rochester.rr.com>; from mbratche@rochester.rr.com on Sat, Jan 27, 2001 at 10:27:03AM -0500
On Sat, Jan 27 2001, Mark Bratcher wrote:
> Hey all,
>
> I applied the patch "loop-3", from Jen Axboe's 2.4.1-pre10 version, to
> my 2.4.0 kernel as Jen had suggested we try for the loop device hang
> problem.
>
> This patch appears to have gotten rid of the problem (at least after
> testing it once in my previous scenario, which would normally fail 100%
> of the time on 2.4.0 official).
>
> Thanks Jen!
First of all, I'm all man (not up for debate) so it's Jens not Jen :-)
> Can I continue running this patch on 2.4.0 with impunity, or do I need
> to be careful of anything else? :-)
It should be safe. Thanks for the feedback.
--
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-28 2:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 3:29 Kernel 2.4.0 loop device still hangs Mark Bratcher
2001-01-27 15:27 ` Mark Bratcher
2001-01-28 2:43 ` Jens Axboe [this message]
2001-01-28 2:50 ` Mark Bratcher
2001-01-28 12:10 ` Mircea Damian
[not found] <fa.hl5rjsv.1b78u0u@ifi.uio.no>
2001-01-26 6:34 ` qkholland
2001-01-26 10:28 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2001-01-28 13:01 Andreas Franck
2001-01-28 19:43 ` Jens Axboe
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=20010128034300.A32375@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbratche@rochester.rr.com \
/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