linux-kernel - Re: [PATCHSET 2.6.22-rc2-mm1] sysfs: assorted fixes

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: <20070529160243.7ea4023d@gondolin.boeblingen.de.ibm.com>
Date:	Tue, 29 May 2007 16:02:43 +0200
From:	Cornelia Huck <cornelia.huck@...ibm.com>
To:	Tejun Heo <htejun@...il.com>
Cc:	gregkh@...e.de, dmitry.torokhov@...il.com, oneukum@...e.de,
	rpurdie@...ys.net, stern@...land.harvard.edu, maneesh@...ibm.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCHSET 2.6.22-rc2-mm1] sysfs: assorted fixes

On Tue, 29 May 2007 01:10:25 +0900,
Tejun Heo <htejun@...il.com> wrote:

> Hello, all.
> 
> This patchset contains two cleanups and three fixes.
> 
> #01: make-sysfs_alloc_ino-static, cleanup
> #02: fix-parent-refcounting, fix
> #03: reorganize-sysfs_new_inode-and-sysfs_create, cleanup and prep for #04
> #04: use-iget_locked-instead-of-new_inode, fix
> #05: fix-root-sysfs_dirent-root-dentry-association, fix
> 
>  fs/sysfs/dir.c   |  143 +++++++++++++++++++++++--------------------------------
>  fs/sysfs/inode.c |  114 ++++++++++++++++++++++++-------------------
>  fs/sysfs/mount.c |   19 ++++---
>  fs/sysfs/sysfs.h |    6 +-
>  4 files changed, 137 insertions(+), 145 deletions(-)
> 
> Please apply.  Thanks.

I've tested this patchset a bit on s390 (device attach/detach and
moving devices around) and didn't encounter problems. As far as I can
see, this looks sane.
-
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/