linux-kernel - Re: 2.6.22-rc4-mm1

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: <46682A25.5070409@gmail.com>
Date:	Thu, 07 Jun 2007 17:54:13 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Tejun Heo <htejun@...il.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Mikael Pettersson <mikpe@...uu.se>,
	linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>
Subject: Re: 2.6.22-rc4-mm1

Tejun Heo napsal(a):
> Jiri Slaby wrote:
>> Tejun Heo napsal(a):
>>> Jiri Slaby wrote:
>>>> Yes. Now I'm compiling -rc4-mm2.
>>> It's probably caused by new sysfs slimdown patches and I'm pretty sure
>>> -rc4-mm2 would fail the same way.  The offending one should be one of
>>> the following patches.
>> There's reverted gregkh-driver-block-device in -mm2. So I wanted to give it a
>> try. Do you think it's pointless and that patch has no impact on the behaviour?
> 
> I'm not familiar with how lvm vgscan works and the patch does look like
> it can affect that.  Please give a shot at -mm2.

Yup, it works without any further patches. So it seems like
gregkh-driver-block-device is the culprit?

regards,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E
-
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/