linux-kernel - Re: [PATCH] sysfs: sysfs_add_one tells you _where

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: <20090211223903.GA21100@suse.de>
Date:	Wed, 11 Feb 2009 14:39:03 -0800
From:	Greg KH <gregkh@...e.de>
To:	Alex Chiang <achiang@...com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sysfs: sysfs_add_one tells you _where_ the duplicate
	file is

On Wed, Feb 11, 2009 at 01:26:01PM -0700, Alex Chiang wrote:
> Give a better clue about where we might be creating duplicate
> files by displaying the parent's name as well.
> 
> Signed-off-by: Alex Chiang <achiang@...com>
> ---
> It would be nice to get a full path, but simply printing out the
> parent is cheap and more useful than what we have now.

What happens if you don't have a parent?  will this oops if you are
creating a duplicate device in the root of the sysfs tree?

thanks,

greg k-h
--
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/