linux-kernel - [PATCHSET] Sysfs cleanups from Eric W. Biederman

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-next>] [day] [month] [year] [list]

Message-Id: <11876133893720-git-send-email-htejun@gmail.com>
Date:	Mon, 20 Aug 2007 21:36:29 +0900
From:	Tejun Heo <htejun@...il.com>
To:	ebiederm@...ssion.com, cornelia.huck@...ibm.com, greg@...ah.com,
	linux-kernel@...r.kernel.org, satyam@...radead.org,
	stern@...land.harvard.edu, containers@...ts.osdl.org,
	htejun@...il.com
Subject: [PATCHSET] Sysfs cleanups from Eric W. Biederman

Hello, all.

This is subset of Eric W. Biederman's "Sysfs cleanups & tagged
directory support" patchset[1] with the following modifications.

* fix-i_mutex-locking-in-sysfs_get_dentry patch is added at the top
  and #14-Don_t-use-lookup_one_len_kern and
  #15-vfs-Remove-lookup_one_len_kern are dropped.  This is because #14
  contained had a bug where it might created dentry/inode for an
  already deleted sysfs_dirent.  I think it's benefitial to keep
  single lookup path.

* Rewrote simplify-sysfs_get_dentry patch and
  #08-Implement-__sysfs_get_dentry,
  #09-Move-sysfs_get_dentry-below-__sysfs_get_dentry and
  #10-Rewrite-sysfs_get_dentry-in-terms-of-__sysfs_get_dentry are
  omitted as __sysfs_get_dentry() isn't used by anyone.

* #16, 19-25 are omitted as it isn't clear yet how the tagged entry
  support will end up.

* readdir simplification fixed.

* sysfs_mutex double locking fixed.

The patchset is on top of the current -gregkh.

Thanks.

--
tejun

[1] http://thread.gmane.org/gmane.linux.kernel/564287/focus=519

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