linux-kernel - Re: [PATCH 2/7] sysfs: Remove first pass at shadow directory support

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

Date:	Tue, 31 Jul 2007 18:17:51 +0530 (IST)
From:	Satyam Sharma <satyam@...radead.org>
To:	Tejun Heo <htejun@...il.com>
cc:	ebiederm@...ssion.com, gregkh@...e.de,
	linux-kernel@...r.kernel.org, cornelia.huck@...ibm.com,
	stern@...land.harvard.edu
Subject: Re: [PATCH 2/7] sysfs: Remove first pass at shadow directory
 support

Hi Tejun,

On Tue, 31 Jul 2007, Tejun Heo wrote:

> Tejun Heo wrote:
> > While shadow directories appear to be a good idea, the current scheme
> > of controlling their creation and destruction outside of sysfs appears
> > to be a locking and maintenance nightmare in the face of sysfs
> > directories dynamically coming and going.  Which can now occur for
> > directories containing network devices when CONFIG_SYSFS_DEPRECATED is
> > not set.
> > 
> > This patch removes everything from the initial shadow directory support
> > that allowed the shadow directory creation to be controlled at a higher
> > level.  So except for a few bits of sysfs_rename_dir everything from
> > commit b592fcfe7f06c15ec11774b5be7ce0de3aa86e73 is now gone.
> 
> "From Eric W. Biederman <ebiederm@...ssion.com>" line is missing.  I
> thought git scripts would add that automatically.  Sorry about that.

I couldn't find this patch in the patchset you just posted ...
-
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/