[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTi=dKXo=TeTU7a--r3YCxrptNU3VVg@mail.gmail.com>
Date: Thu, 19 May 2011 20:12:44 +0200
From: Tejun Heo <tj@...nel.org>
To: Greg KH <gregkh@...e.de>
Cc: linux-kernel@...r.kernel.org, stable@...nel.org,
stable-review@...nel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
Jens Axboe <jaxboe@...ionio.com>
Subject: Re: [57/71] block: rescan partitions on invalidated devices on
-ENOMEDIA too
Hello, Greg.
On Thu, May 19, 2011 at 8:05 PM, Greg KH <gregkh@...e.de> wrote:
>
> 2.6.38-stable review patch. If anyone has any objections, please let us know.
>
> ------------------
>
> From: Tejun Heo <tj@...nel.org>
>
> commit 02e352287a40bd456eb78df705bf888bc3161d3f upstream.
>
> __blkdev_get() doesn't rescan partitions if disk->fops->open() fails,
> which leads to ghost partition devices lingering after medimum removal
> is known to both the kernel and userland. The behavior also creates a
> subtle inconsistency where O_NONBLOCK open, which doesn't fail even if
> there's no medium, clears the ghots partitions, which is exploited to
> work around the problem from userland.
>
> Fix it by updating __blkdev_get() to issue partition rescan after
> -ENOMEDIA too.
>
> This was reported in the following bz.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=13029
>
> Stable: 2.6.38
>
Can you please hold this for a while? It causes an extra warning
message to be printed during device detection. It isn't harmful but
still. I'll soon send a patch to resolve the issue and it would be
better for them to go together.
Thank you.
--
tejun
--
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/
Powered by blists - more mailing lists