From: Sasha Levin <levinsasha928@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jan Kara <jack@suse.cz>, Tejun Heo <tj@kernel.org>,
axboe@kernel.dk, Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
ben@decadent.org.uk
Subject: Re: blk: NULL ptr deref in blk_dequeue_request()
Date: Tue, 09 Oct 2012 09:21:59 -0400 [thread overview]
Message-ID: <507424F7.60801@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1210082340501.19980@pobox.suse.cz>
On 10/08/2012 05:45 PM, Jiri Kosina wrote:
> On Mon, 8 Oct 2012, Jan Kara wrote:
>
>>> > > I'm still seeing this on linux-next.
>> > I think this is floppy related (see redo_fd_request() in the stack
>> > trace). And there were quite some changes to the area recently. Adding
>> > maintainer to CC.
> Hmm ... I don't immediately see how this is happening.
>
> Sasha, could you please do git bisect on drivers/block/floppy.c between
> f6365201d and your git HEAD for starters (assuming that f6365201d works
> well for you?).
>
A bisect on floppy.c yielded the following:
b33d002f4b6bae912463e5a66387c498aa69b6fe is the first bad commit
commit b33d002f4b6bae912463e5a66387c498aa69b6fe
Author: Ben Hutchings <ben@decadent.org.uk>
Date: Mon Aug 27 20:56:53 2012 -0300
genhd: Make put_disk() safe for disks that have not been registered
Thanks,
Sasha
next prev parent reply other threads:[~2012-10-09 13:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 20:35 blk: NULL ptr deref in blk_dequeue_request() Sasha Levin
2012-10-07 18:26 ` Sasha Levin
2012-10-08 17:22 ` Jan Kara
2012-10-08 21:45 ` Jiri Kosina
2012-10-09 13:21 ` Sasha Levin [this message]
2012-10-09 13:26 ` Sasha Levin
2012-10-10 15:52 ` Ben Hutchings
2012-10-12 14:51 ` Jiri Kosina
2012-10-12 17:55 ` Sasha Levin
2012-10-17 1:29 ` Ben Hutchings
2012-10-17 14:11 ` Jiri Kosina
2012-10-17 14:23 ` Jens Axboe
2012-10-26 18:00 ` Jiri Kosina
2012-10-17 1:30 ` Ben Hutchings
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=507424F7.60801@gmail.com \
--to=levinsasha928@gmail.com \
--cc=axboe@kernel.dk \
--cc=ben@decadent.org.uk \
--cc=davej@redhat.com \
--cc=jack@suse.cz \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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