From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Dyer <nick.dyer@itdev.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysfs: Fix null pointer dereference caused by sysfs_notify on binary attribute
Date: Thu, 6 Jun 2013 12:37:52 -0700 [thread overview]
Message-ID: <20130606193752.GA22115@kroah.com> (raw)
In-Reply-To: <1370511920-8628-1-git-send-email-nick.dyer@itdev.co.uk>
On Thu, Jun 06, 2013 at 10:45:20AM +0100, Nick Dyer wrote:
> If sysfs_notify is called on a binary attribute, bad things can
> happen, so prevent it.
>
> Note, no in-kernel usage of this is currently present, but in the
> future, it's good to be safe.
>
> Signed-off-by: Nick Dyer <nick.dyer@itdev.co.uk>
> ---
> fs/sysfs/file.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/fs/sysfs/file.c b/fs/sysfs/file.c
> index 602f56d..976819b 100644
> --- a/fs/sysfs/file.c
> +++ b/fs/sysfs/file.c
> @@ -449,10 +449,12 @@ void sysfs_notify_dirent(struct sysfs_dirent *sd)
>
> spin_lock_irqsave(&sysfs_open_dirent_lock, flags);
>
> - od = sd->s_attr.open;
> - if (od) {
> - atomic_inc(&od->event);
> - wake_up_interruptible(&od->poll);
> + if (sd->s_attr) {
> + od = sd->s_attr.open;
> + if (od) {
> + atomic_inc(&od->event);
> + wake_up_interruptible(&od->poll);
> + }
Please test build your patches, it makes kernel maintainers very grumpy
when you send them patches that are obviously broken :(
greg k-h
next prev parent reply other threads:[~2013-06-06 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 9:45 [PATCH] Fix null pointer dereference caused by sysfs_notify on binary attribute Nick Dyer
2013-06-06 15:26 ` Greg KH
2013-06-06 15:36 ` Nick Dyer
2013-06-06 19:37 ` Greg KH [this message]
2013-06-07 14:45 ` [PATCH V2] sysfs_notify is only possible on file attributes Nick Dyer
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=20130606193752.GA22115@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.dyer@itdev.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.