All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Alessandro Zummo <alessandro.zummo@towertech.it>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Marcin Slusarz <marcin.slusarz@gmail.com>,
	linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
	stable@kernel.org
Subject: Re: [PATCH] rtc: fix kernel panic on second use of SIGIO nofitication
Date: Thu, 2 Oct 2008 16:44:51 -0700	[thread overview]
Message-ID: <200810021644.51962.david-b@pacbell.net> (raw)
In-Reply-To: <20081003001238.7030c151@i1501.lan.towertech.it>

On Thursday 02 October 2008, Alessandro Zummo wrote:
> On Thu, 2 Oct 2008 14:49:41 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > On Sun, 14 Sep 2008 20:11:27 +0200
> > Marcin Slusarz <marcin.slusarz@gmail.com> wrote:
> > 
> > > When user space uses SIGIO notification and forgets to disable it before
> > > closing file descriptor, rtc->async_queue contains stale pointer to struct
> > > file. When user space enables again SIGIO notification in different process,
> > > kernel dereferences this (poisoned) pointer and crashes.
> > > 
> > > So disable SIGIO notification on close.
> > > 
> > 
> > David, Alessandro: can we please have a review-n-ack of this one for
> > 2.6.27 and earlier?  
> > 
> > Thanks.
> > 
> > From: Marcin Slusarz <marcin.slusarz@gmail.com>
> > 
> > When userspace uses SIGIO notification and forgets to disable it before
> > closing file descriptor, rtc->async_queue contains stale pointer to struct
> > file.  When user space enables again SIGIO notification in different
> > process, kernel dereferences this (poisoned) pointer and crashes.
> > 
> > So disable SIGIO notification on close.
> 
>  [...]
> > 
> > Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
> > Cc: Alessandro Zummo <alessandro.zummo@towertech.it>
> > Cc: David Brownell <dbrownell@users.sourceforge.net>
> > Cc: <stable@kernel.org>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> 
>  
>  Acked-by: Alessandro Zummo <a.zummo@towertech.it>

Acked-by: David Brownell <dbrownell@users.sourceforge.net>

Seemed "obviously good" anti-oops medicine to me, then I double
checked against some code that is AFAIK still correct..

      reply	other threads:[~2008-10-02 23:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 18:11 [PATCH] rtc: fix kernel panic on second use of SIGIO nofitication Marcin Slusarz
2008-10-02 21:49 ` Andrew Morton
2008-10-02 22:12   ` Alessandro Zummo
2008-10-02 23:44     ` David Brownell [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=200810021644.51962.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --cc=alessandro.zummo@towertech.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=rtc-linux@googlegroups.com \
    --cc=stable@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 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.