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]

Date:	Thu, 07 Jun 2007 09:15:33 +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
Subject: Re: 2.6.22-rc4-mm1

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?

> gregkh-driver-sysfs-fix-parent-refcounting-during-rename-and-move.patch
> gregkh-driver-sysfs-reorganize-sysfs_new_indoe-and-sysfs_create.patch
> gregkh-driver-sysfs-use-iget_locked-instead-of-new_inode.patch
> gregkh-driver-sysfs-fix-root-sysfs_dirent-root-dentry-association.patch
> gregkh-driver-sysfs-move-s_active-functions-to-fs-sysfs-dirc.patch
> gregkh-driver-sysfs-slim-down-sysfs_dirent-s_active.patch
> gregkh-driver-sysfs-use-singly-linked-list-for-sysfs_dirent-tree.patch
> 
> Can you bisect the above patches?

Sure, in 12 hours or tomorrow.

thanks,
-- 
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/