LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Ken Chen" <kenchen@google.com>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: "Eric Dumazet" <dada1@cosmosbay.com>, "Tomas M" <tomas@slax.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] max_loop limit
Date: Sat, 24 Mar 2007 17:17:18 -0700 [thread overview]
Message-ID: <b040c32a0703241717t5fc33fc5ke645708d12b6e5cb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0703240023220.10028@yvahk01.tjqt.qr>
On 3/23/07, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
> Sadly, it locks up the foreground process (losetup that would be), and I
> have not yet figured out why. And the mpt regression elsewhere is
> hindering me in finding out faster.
You need to tell the block layer that each loop device is a whole
block device, not a partition within another device. Otherwise, I
think it will cause a recursive mutex lock in block_dev.c:do_open().
This patch should fix the problem.
Signed-off-by: Ken Chen <kenchen@google.com>
--- ./drivers/block/loop.c.orig 2007-03-24 17:05:51.000000000 -0700
+++ ./drivers/block/loop.c 2007-03-24 17:06:06.000000000 -0700
@@ -1464,6 +1464,7 @@
if ((lo = loop_find_dev(number)) == NULL) {
lo = loop_init_one(number);
+ *part = 0;
if (IS_ERR(lo))
return (void *)lo;
}
next prev parent reply other threads:[~2007-03-25 0:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 7:57 Tomas M
2007-03-22 11:00 ` markus reichelt
2007-03-22 11:37 ` Tomas M
2007-03-22 13:42 ` Eric Dumazet
2007-03-22 13:42 ` Jens Axboe
2007-03-22 13:52 ` Eric Dumazet
2007-03-22 13:54 ` Jens Axboe
2007-03-22 14:11 ` William Lee Irwin III
2007-03-22 15:22 ` Arjan van de Ven
2007-03-22 16:09 ` Pádraig Brady
2007-03-28 23:34 ` Karel Zak
[not found] ` <20070322151826.c1421851.dada1@cosmosbay.com>
[not found] ` <20070322142306.GU19922@kernel.dk>
[not found] ` <20070322153603.1f5d442d.dada1@cosmosbay.com>
2007-03-22 15:31 ` max_loop limit - paid job offer Tomas M
2007-03-22 14:33 ` max_loop limit Al Viro
2007-03-22 19:51 ` Olivier Galibert
2007-03-22 14:25 ` Tomas M
2007-03-23 1:34 ` Jan Engelhardt
2007-03-23 23:26 ` [PATCH] " Jan Engelhardt
2007-03-25 0:17 ` Ken Chen [this message]
2007-03-25 0:29 ` Ken Chen
2007-03-25 8:40 ` Tomas M
2007-03-28 23:41 ` Karel Zak
2007-03-29 3:54 ` Kyle Moffett
2007-03-29 4:16 ` [PATCH] max_loop limit, t2 Jan Engelhardt
2007-03-29 8:38 ` [PATCH] max_loop limit, loop.c final working version Tomas M
2007-03-29 14:16 ` max_loop limit Bill Davidsen
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=b040c32a0703241717t5fc33fc5ke645708d12b6e5cb@mail.gmail.com \
--to=kenchen@google.com \
--cc=dada1@cosmosbay.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas@slax.org \
--subject='Re: [PATCH] max_loop limit' \
/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
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).