From: Greg KH <gregkh@suse.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: Drivers <Drivers@analog.com>,
stable@kernel.org, torvalds@linux-foundation.org,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: patch "Staging: iio: adis16220: fix up some sysfs attribute permissions" added to staging tree
Date: Thu, 18 Nov 2010 10:02:11 -0800 [thread overview]
Message-ID: <20101118180211.GA5155@suse.de> (raw)
In-Reply-To: <4CE5684A.8070404@cam.ac.uk>
On Thu, Nov 18, 2010 at 05:54:18PM +0000, Jonathan Cameron wrote:
> On 11/18/10 17:19, Greg KH wrote:
> > On Thu, Nov 18, 2010 at 05:05:05PM +0000, Jonathan Cameron wrote:
> >> On 11/16/10 19:25, gregkh@suse.de wrote:
> >>>
> >>> This is a note to let you know that I've just added the patch titled
> >>>
> >>> Staging: iio: adis16220: fix up some sysfs attribute permissions
> >>>
> >>> to my staging git tree which can be found at
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6.git
> >>> in the staging-linus branch.
> >>>
> >>> The patch will show up in the next release of the linux-next tree
> >>> (usually sometime within the next 24 hours during the week.)
> >>>
> >>> The patch will hopefully also will be merged in Linus's tree for the
> >>> next -rc kernel release.
> >>>
> >>> If you have any questions about this process, please let me know.
> >>>
> >>>
> >>> >From 1d904e8950c86e670ace237eaea1d48cd81e94df Mon Sep 17 00:00:00 2001
> >>> From: Greg Kroah-Hartman <gregkh@suse.de>
> >>> Date: Tue, 16 Nov 2010 11:19:53 -0800
> >>> Subject: Staging: iio: adis16220: fix up some sysfs attribute permissions
> >>>
> >>> They should not be writable by any user
> >> Sorry Greg, it may be jet lag related, but I really don't see how this change
> >> makes sense... Doesn't this take a write only parameter and make it read only
> >> with no read function defined? Was the intent to restrict who could write
> >> to this attribute?
> >
> > Ah crap.
> >
> >>> #define IIO_DEV_ATTR_CAPTURE(_store) \
> >>> - IIO_DEVICE_ATTR(capture, S_IWUGO, NULL, _store, 0)
> >>> + IIO_DEVICE_ATTR(capture, S_IRUSR, NULL, _store, 0)
> >
> > This should be S_IWUSR, right?
> Equivalent with that in and I'm happy to add my ack.
>
> Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
Thanks.
And yes, I got all 7 of these patches wrong, I'll go redo them :(
thanks for verifying and actually reviewing them, I appreciate it.
greg k-h
prev parent reply other threads:[~2010-11-18 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12899355293477@site>
2010-11-18 17:05 ` patch "Staging: iio: adis16220: fix up some sysfs attribute permissions" added to staging tree Jonathan Cameron
2010-11-18 17:19 ` Greg KH
2010-11-18 17:54 ` Jonathan Cameron
2010-11-18 18:02 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101118180211.GA5155@suse.de \
--to=gregkh@suse.de \
--cc=Drivers@analog.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox