| 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
| ||
|
Message-ID: <1499926.Jx7HlHxHXb@wuerfel> Date: Mon, 14 Sep 2015 17:25:23 +0200 From: Arnd Bergmann <arnd@...db.de> To: linaro-kernel@...ts.linaro.org Cc: Viresh Kumar <viresh.kumar@...aro.org>, gregkh@...uxfoundation.org, sboyd@...eaurora.org, Rafael Wysocki <rjw@...ysocki.net>, open list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] debugfs: don't access 4 bytes for a boolean On Friday 11 September 2015 14:36:06 Viresh Kumar wrote: > > debugfs_create_bool() declares the pointer to be of type u32 *. > Shouldn't that be changed to u8 *? There are many users which are > typecasting the variables to make debugfs API happy I'd say that the argument to debugfs_create_bool() has to match the access in the functions you are modifying, as well as whatever gets passed into it by callers. By accessing only the first byte, you break all drivers that call debugfs_create_bool() with a four-byte argument, at least on big-endian systems! If we change any part of this, we need to audit the existing 31 callers of the function and change them all to use a bool type. In the problem that you saw, what prevented gcc from printing a compile-time warning about debugfs_create_bool() being called with a bool argument? Arnd -- 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