linux-kernel - Re: linux-next: Tree for August 14 (sysfs/acpi errors)

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: <87hc9kxpp8.fsf@basil.nowhere.org>
Date:	Sun, 17 Aug 2008 05:53:07 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Greg KH <greg@...ah.com>
Cc:	Kay Sievers <kay.sievers@...y.org>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org, rusty@...tcorp.com.au
Subject: Re: linux-next: Tree for August 14 (sysfs/acpi errors)

Greg KH <greg@...ah.com> writes:
>> No!
>
> What you are doing here is wrong, trying to create two files with the
> same name.  You just should not be doing that at all, it's that simple.
> Fix the broken code/link order, don't paper it over in the sysfs layer.

Sorry, but relying on link order for anything is a mistake. It is subtle
and fragile and just means it'll eventually break again because it's
near impossible to properly maintain.

The alternative is to always check if the file exists in the params.c
code before creating it. We can do that too, but it's somewhat dumb
because sysfs is already doing that.

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