linux-kernel - Re: [rtmutex-tester] WARNING: at drivers/base/core.c:569 device_create

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] [day] [month] [year] [list]

Message-ID: <20130329163424.GA3380@kroah.com>
Date:	Fri, 29 Mar 2013 09:34:24 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Kay Sievers <kay.sievers@...y.org>, Felipe Balbi <balbi@...com>,
	linux-kernel@...r.kernel.org
Subject: Re: [rtmutex-tester] WARNING: at drivers/base/core.c:569
 device_create_file()

On Fri, Mar 29, 2013 at 10:17:04AM +0800, Fengguang Wu wrote:
> Hi Kay,
> 
> I got the below warning and the first "bad" commit is
> 
> commit 8f46baaa7ec6cd0851794020b31958e64679dd26
> Author: Felipe Balbi <balbi@...com>
> Date:   Wed Feb 20 10:31:42 2013 +0200
> 
>     base: core: WARN() about bogus permissions on device attributes
>     
>     Whenever a struct device_attribute is registered
>     with mismatched permissions - read permission without
>     a show routine or write permission without store
>     routine - we will issue a big warning so we catch
>     those early enough.
>     
>     Signed-off-by: Felipe Balbi <balbi@...com>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>

That's just a "warning" patch, I'll fix this up properly
(kernel/rtmutex-tester.c has 0600 as the mode for a read-only attribute
as well as a write-only attribute.)

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/