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: <20151007220807.GA3375@localhost> Date: Wed, 7 Oct 2015 15:08:07 -0700 From: Olof Johansson <olof@...om.net> To: Greg KH <gregkh@...uxfoundation.org> Cc: Emilio L?pez <emilio.lopez@...labora.co.uk>, kgene@...nel.org, k.kozlowski@...sung.com, linux@...ck-us.net, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org Subject: Re: [PATCH 1/4] sysfs: Support is_visible() on binary attributes On Sun, Oct 04, 2015 at 07:33:34PM +0100, Greg KH wrote: > On Mon, Sep 21, 2015 at 10:38:20AM -0300, Emilio L?pez wrote: > > According to the sysfs header file: > > > > "The returned value will replace static permissions defined in > > struct attribute or struct bin_attribute." > > > > but this isn't the case, as is_visible is only called on struct attribute > > only. This patch introduces a new is_bin_visible() function to implement > > the same functionality for binary attributes, and updates documentation > > accordingly. > > > > Note that to keep functionality and code similar to that of normal > > attributes, the mode is now checked as well to ensure it contains only > > read/write permissions or SYSFS_PREALLOC. > > > > Reviewed-by: Guenter Roeck <linux@...ck-us.net> > > Signed-off-by: Emilio L?pez <emilio.lopez@...labora.co.uk> > > As this should probably go through the "platform drivers" maintainer, > I'll just give you this: > > Acked-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> > > So it can go through their tree and not require me to just take this > one. Thanks, applied to the chrome-platform tree now. -Olof -- 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