linux-kernel - Re: [PATCH] SYSFS: Allow boot time switching between deprecated and modern sysfs layout

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: <20100908160235.61ae1200@basil.nowhere.org>
Date:	Wed, 8 Sep 2010 16:02:35 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Greg KH <greg@...ah.com>
Cc:	Kay Sievers <kay.sievers@...y.org>, linux-kernel@...r.kernel.org,
	Andi Kleen <ak@...ux.intel.com>, axboe@...nel.dk,
	tiwai@...e.de, James.Bottomley@...senPartnership.com
Subject: Re: [PATCH] SYSFS: Allow boot time switching between deprecated and
 modern sysfs layout

On Wed, 8 Sep 2010 06:55:30 -0700
Greg KH <greg@...ah.com> wrote:

> But, Kay and I just changed the logic in the kernel in this area,
> getting rid of the CONFIG_SYSFS_DEPRECATED_V2 option entirely, to try
> to make the code path smaller, only offering the "old" mode for block
> devices, to keep kernels booting on userspace instances like what you
> have.

That will likely break my user space, it relies on the old style
net set up (opensuse 10.0) for network configuration. 
That was the main reason I did this patch.


> 
> So, could you respin this patch against the linux-next tree which has
> Kay's patch in it?  Or, if it's easier, I've attached the patch below.

I can test your patch first, but to be honest I doubt it'll work on the
10.0 roots.

-Andi


-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/