From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Ray Lee <ray-lk@madrabbit.org>, Al Viro <viro@ftp.linux.org.uk>,
Andrey Borzenkov <arvidjaar@mail.ru>,
Uwe Bugla <uwe.bugla@gmx.de>, Ken Chen <kenchen@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image
Date: Mon, 21 May 2007 09:11:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705210908170.3890@woody.linux-foundation.org> (raw)
In-Reply-To: <1179677799.3311.5.camel@lov.localdomain>
On Sun, 20 May 2007, Kay Sievers wrote:
>
> Right, providing "preallocated" devices, 8 or the number given in
> max_loop, sounds like the best option until the tools can handle that.
Yes. Can somebody who actually _uses_ loop send a tested patch, please?
We're not going to break existing user space over something idiotic like
this. Not acceptable.
The alternative is to just revert all the loop.c patches. Which I'll do
unless somebody sends me a tested fix - because as a non-loop user myself,
I don't have much choice. I assume it is
commit 73285082 "remove artificial software max_loop limit"
that introduced the new behaviour. Ken?
Linus
next prev parent reply other threads:[~2007-05-21 16:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 18:33 Ray Lee
2007-05-19 19:17 ` Andrey Borzenkov
[not found] ` <200705200124.13026.uwe.bugla@gmx.de>
2007-05-20 4:45 ` Andrey Borzenkov
2007-05-20 6:16 ` Ray Lee
2007-05-20 6:28 ` Al Viro
2007-05-20 6:58 ` Andrey Borzenkov
2007-05-20 14:52 ` Uwe Bugla
2007-05-20 15:26 ` Ray Lee
2007-05-20 15:22 ` Ray Lee
2007-05-20 15:54 ` Kay Sievers
2007-05-20 16:02 ` Andrey Borzenkov
2007-05-20 16:23 ` Andreas Schwab
2007-05-20 16:10 ` Ray Lee
2007-05-20 16:16 ` Kay Sievers
2007-05-20 16:29 ` Uwe Bugla
2007-05-20 19:53 ` Michael Mauch
2007-05-21 16:11 ` Linus Torvalds [this message]
2007-05-21 16:27 ` Ken Chen
2007-05-21 16:35 ` Ray Lee
2007-05-21 16:37 ` Ken Chen
2007-05-21 16:50 ` Uwe Bugla
2007-05-21 17:11 ` Kay Sievers
2007-05-21 17:51 ` Andrey Borzenkov
2007-05-21 17:04 ` Linus Torvalds
2007-05-21 20:48 ` Ken Chen
2007-05-21 21:20 ` Uwe Bugla
2007-05-21 22:04 ` Andrew Morton
2007-05-22 0:10 ` Al Viro
2007-05-22 0:13 ` Al Viro
2007-05-20 16:09 ` Andrey Borzenkov
2007-05-20 16:14 ` Ray Lee
2007-05-22 20:18 ` Jan Engelhardt
2007-05-22 21:35 ` Uwe Bugla
2007-05-21 6:08 ` Ken Chen
2007-05-21 6:40 ` Ray Lee
2007-05-21 7:59 ` Uwe Bugla
-- strict thread matches above, loose matches on Subject: below --
2007-05-19 13:53 Uwe Bugla
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=alpine.LFD.0.98.0705210908170.3890@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=arvidjaar@mail.ru \
--cc=kay.sievers@vrfy.org \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=ray-lk@madrabbit.org \
--cc=uwe.bugla@gmx.de \
--cc=viro@ftp.linux.org.uk \
/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
all inboxes | Powered by JetHome®