linux-kernel - Re: [STABLE PATCH .26 .27] ACPI: avoid empty file name in sysfs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1226886012.15014.231.camel@rzhang-dt>
Date:	Mon, 17 Nov 2008 09:40:12 +0800
From:	Zhang Rui <rui.zhang@...el.com>
To:	Pavel Machek <pavel@...e.cz>
Cc:	Len Brown <lenb@...nel.org>,
	"stable@...nel.org" <stable@...nel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [STABLE PATCH .26 .27] ACPI: avoid empty file name in sysfs

On Sun, 2008-11-16 at 01:17 +0800, Pavel Machek wrote:
> Hi!
> 
> > upstream 4feba70a2c1a1a0c96909f657f48b2e11e682370
> > 
> > Since commit bc45b1d39a925b56796bebf8a397a0491489d85c acpi tables are
> > allowed to have an empty signature and /sys/firmware/acpi/tables uses the
> > signature as filename.  Applications using naive recursion through /sys
> > loop forever.  A possible solution would be: (replacing the zero length
> > filename with the string "NULL")
> 
> What about using some string that is not a valid table name? Shorter
> than 4 characters? AFAICT,
> 'NULL' table could be added to acpi in future...?
> 
> What if *two* tales have empty signature?
there are "NULL1" and "NULL2" in this case.

thanks,
rui

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