public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Dyer <nick.dyer@itdev.co.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix null pointer dereference caused by sysfs_notify on binary attribute
Date: Thu, 06 Jun 2013 16:36:45 +0100	[thread overview]
Message-ID: <51B0AC8D.3070708@itdev.co.uk> (raw)
In-Reply-To: <20130606152612.GA7495@kroah.com>

Greg KH wrote:
> On Thu, Jun 06, 2013 at 10:45:20AM +0100, Nick Dyer wrote:
>> It would be nice to have this work as expected but for now this is a minimal
>> fix to prevent the kernel panic.
> 
> Is anyone calling sysfs_notify on a binary attribute today?  Or can this
> go into 3.11?

Nope. I think I'm the first person to try it. So 3.11 is fine.

  reply	other threads:[~2013-06-06 15:36 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 [this message]
2013-06-06 19:37 ` [PATCH] sysfs: " Greg KH
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=51B0AC8D.3070708@itdev.co.uk \
    --to=nick.dyer@itdev.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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