linux-kernel - Re: bug in 2.6.22-rc2: loop mount limited to one single iso image

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b040c32a0705210927q24e2cd8fm9f4616941fccfdea@mail.gmail.com>
Date:	Mon, 21 May 2007 09:27:44 -0700
From:	"Ken Chen" <kenchen@...gle.com>
To:	"Linus Torvalds" <torvalds@...ux-foundation.org>
Cc:	"Kay Sievers" <kay.sievers@...y.org>,
	"Ray Lee" <ray-lk@...rabbit.org>,
	"Al Viro" <viro@....linux.org.uk>,
	"Andrey Borzenkov" <arvidjaar@...l.ru>,
	"Uwe Bugla" <uwe.bugla@....de>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
Subject: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image

On 5/21/07, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 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?

yes and no. in that commit, I automatically create n+1 device when
loop device n is created, allergically was tested to be fine with
casual usage of "losetup" and "mount -o loop".  However, there is a
bug in that commit when loop.c was compiled as a module.  And when Al
fixed it, he also removed that magic "n+1" trick.

Nevertheless, yes, I'm guilty of introducing the new behavior.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/