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: <2c0942db0705192316s2682807chd23df6f4de29edcb@mail.gmail.com>
Date:	Sat, 19 May 2007 23:16:59 -0700
From:	"Ray Lee" <ray-lk@...rabbit.org>
To:	"Andrey Borzenkov" <arvidjaar@...l.ru>
Cc:	"Uwe Bugla" <uwe.bugla@....de>, "Ken Chen" <kenchen@...gle.com>,
	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/19/07, Andrey Borzenkov <arvidjaar@...l.ru> wrote:
> On Sunday 20 May 2007, Uwe Bugla wrote:
> > unfortunately it does not make any difference if I simply rip out the
> > changes of patch-2.6.22-rc2 or patch-2.6.21 in connection with patch
> > 2.6.22-rc2 regarding module loop.c.
>
> because they are just followup to the real cause. This is causes by commit
>
> commit 73285082745045bcd64333c1fbaa88f8490f2626
> Author: Ken Chen <kenchen@...gle.com>
> Date:   Tue May 8 00:28:20 2007 -0700
>
>     remove artificial software max_loop limit
>

Yeah, that's the only one left. I was hoping it wasn't that one, as it
claimed to have been tested extensively. Guess it wasn't tested with
udev.

Ken? Ball's in your court. As the patch isn't providing a killer
feature for 2.6.22, I'd suggest just reverting it for now until the
issues are ironed out.

Ray
-
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/