From: Tejun Heo <htejun@gmail.com>
To: ebiederm@xmission.com, cornelia.huck@de.ibm.com, greg@kroah.com,
linux-kernel@vger.kernel.org, satyam@infradead.org,
stern@rowland.harvard.edu, containers@lists.osdl.org,
htejun@gmail.com
Subject: [PATCHSET] Sysfs cleanups from Eric W. Biederman
Date: Mon, 20 Aug 2007 21:36:29 +0900 [thread overview]
Message-ID: <11876133893720-git-send-email-htejun@gmail.com> (raw)
In-Reply-To:
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
next reply other threads:[~2007-08-20 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 12:36 Tejun Heo [this message]
2007-08-20 12:36 ` [PATCH 01/14] sysfs: fix i_mutex locking in sysfs_get_dentry() Tejun Heo
2007-08-20 12:36 ` [PATCH 12/14] sysfs: kill SYSFS_FLAG_REMOVED Tejun Heo
2007-08-20 12:36 ` [PATCH 10/14] sysfs: simply sysfs_get_dentry Tejun Heo
2007-08-22 9:26 ` [PATCHSET] Sysfs cleanups from Eric W. Biederman Cornelia Huck
2007-08-22 9:39 ` Tejun Heo
2007-08-22 14:04 ` Eric W. Biederman
2007-08-22 14:45 ` Tejun Heo
2007-08-22 15:51 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11876133893720-git-send-email-htejun@gmail.com \
--to=htejun@gmail.com \
--cc=containers@lists.osdl.org \
--cc=cornelia.huck@de.ibm.com \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=satyam@infradead.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).