From: Momchil Velikov <velco@fadata.bg>
To: "David Gomez" <davidge@jazzfree.com>
Cc: Dave Jones <davej@suse.de>, Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Copying to loop device hangs up everything
Date: 16 Dec 2001 18:53:27 +0200 [thread overview]
Message-ID: <87snab85tk.fsf@fadata.bg> (raw)
In-Reply-To: <Pine.LNX.4.33.0112161231570.650-100000@fargo>
In-Reply-To: <Pine.LNX.4.33.0112161231570.650-100000@fargo>
>>>>> "David" == David Gomez <davidge@jazzfree.com> writes:
David> On Sun, 16 Dec 2001, Dave Jones wrote:
>> > I'm using kernel 2.4.17-rc1 and found what i think is a bug, maybe related
>> > to the loop device. This is the situation:
>>
>> Can you repeat it with this applied ?
>> ftp://ftp.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.17rc1aa1/00_loop-deadlock-1
David> Thanks ;), this patch solves the problem and copying a lot of data to the
David> loop device now doesn't hang the computer.
David> Is this patch going to be applied to the stable kernel ? Marcelo ?
I've had exactly the same hangups with or without the patch.
next prev parent reply other threads:[~2001-12-16 18:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 3:40 Copying to loop device hangs up everything David Gomez
2001-12-16 4:00 ` Dave Jones
2001-12-16 11:41 ` David Gomez
2001-12-16 16:53 ` Momchil Velikov [this message]
2001-12-16 19:42 ` David Gomez
2001-12-16 19:50 ` Momchil Velikov
2001-12-16 21:52 ` Momchil Velikov
2001-12-18 19:46 ` Marcelo Tosatti
2001-12-18 20:54 ` Momchil Velikov
2001-12-18 19:57 ` Marcelo Tosatti
2001-12-18 21:26 ` Momchil Velikov
[not found] ` <3C1FC254.525B9108@zip.com.au>
[not found] ` <3C1FCB96.83E49ECB@zip.com.au>
[not found] ` <3C204C4F.C989AD71@zip.com.au>
2001-12-19 13:42 ` Andrea Arcangeli
2001-12-20 7:41 ` Andrew Morton
2001-12-20 11:27 ` Andrea Arcangeli
2001-12-20 11:34 ` Andrea Arcangeli
2001-12-17 3:30 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2001-12-20 21:05 Momchil Velikov
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=87snab85tk.fsf@fadata.bg \
--to=velco@fadata.bg \
--cc=davej@suse.de \
--cc=davidge@jazzfree.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.