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
| ||
|
Date: Sat, 15 Aug 2015 13:48:50 +0600 From: Alexander Kuleshov <kuleshovmail@...il.com> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Tony Luck <tony.luck@...el.com>, Pekka Enberg <penberg@...nel.org>, Mel Gorman <mgorman@...e.de>, Baoquan He <bhe@...hat.com>, Tang Chen <tangchen@...fujitsu.com>, Robin Holt <holt@....com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: Re: [PATCH] mm/memblock: validate the creation of debugfs files On 08-15-15, Andrew Morton wrote: > Yes, I agree that if memblock's debugfs_create_file() fails, we want to > know about it because something needs fixing. But that's true of > all(?) debugfs_create_file callsites, so it's a bit silly to add > warnings to them all. Why not put the warning into > debugfs_create_file() itself? Good idea, but there are already some debugfs_create_file calls with checks and warning, if these checks failed. I don't know how many, but I saw it. Double warning is not good too. -- 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/
Powered by blists - more mailing lists