linux-kernel - Re: [PATCH v2 1/4] debugfs: Implement debugfs_remove

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]

Date:	Tue, 1 Jul 2008 11:37:33 -0700
From:	Greg KH <greg@...ah.com>
To:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>
Cc:	Pierre Ossman <drzeus-list@...eus.cx>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/4] debugfs: Implement debugfs_remove_recursive()

On Tue, Jul 01, 2008 at 03:14:51PM +0200, Haavard Skinnemoen wrote:
> debugfs_remove_recursive() will remove a dentry and all its children.
> Drivers can use this to zap their whole debugfs tree so that they don't
> need to keep track of every single debugfs dentry they created.
> 
> It may fail to remove the whole tree in certain cases:
> 
> sh-3.2# rmmod atmel-mci < /sys/kernel/debug/mmc0/ios/clock
> mmc0: card b368 removed
> atmel_mci atmel_mci.0: Lost dma0chan1, falling back to PIO
> sh-3.2# ls /sys/kernel/debug/mmc0/
> ios
> 
> But I'm not sure if that case can be handled in any sane manner.
> 
> Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@...el.com>
> Cc: Greg KH <greg@...ah.com>

If this is tied to some other series that needs to go through some other
maintainer, feel free to add:
	Acked-by: Greg Kroah-Hartman <gregkh@...e.de>
to the patch and let someone else take it.

Otherwise, if you need me to take it, I will be glad to do so, just let
me know what is easiest for you.

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/