From: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
To: Tejun Heo <tj@kernel.org>
Cc: Vivek Goyal <vgoyal@redhat.com>,
Suresh Jayaraman <sjayaraman@suse.com>,
LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>
Subject: Re: Slab corruption in floppy driver module
Date: Thu, 26 Jan 2012 19:53:07 +0100 [thread overview]
Message-ID: <gisjj25m98.fsf@mx10.gouders.net> (raw)
In-Reply-To: <20120126180532.GA4077@dhcp-172-17-108-109.mtv.corp.google.com> (Tejun Heo's message of "Thu, 26 Jan 2012 10:05:32 -0800")
Tejun Heo <tj@kernel.org> writes:
> Hello,
>
> On Thu, Jan 26, 2012 at 10:04:20AM -0500, Vivek Goyal wrote:
>> out_put_disk:
>> while (dr--) {
>> del_timer_sync(&motor_off_timer[dr]);
>> - if (disks[dr]->queue)
>> + if (disks[dr]->queue) {
>> blk_cleanup_queue(disks[dr]->queue);
>> + /*
>> + * The request queue reference we took at device
>> + * creation time has been put by above
>> + * blk_cleanup_queue(). We have not called add_disk()
>> + * yet and due to failure calling put_disk(). Put disk
>> + * will try to put a reference to disk->queue which is
>> + * taken in add_disk(). As we have not taken that
>> + * extra reference, putting extra reference down
>> + * will try to access already freed queue. Clear
>> + * disk->queue before calling put_disk().
>> + */
>> + disks[dr]->queue = NULL;
>
> Yeah, this looks correct to me. It might be better to tone down the
> comment a bit tho. Wouldn't it be sufficient to say put_disk() isn't
> paired with add_disk() and will put one extra time?
I tested the patch on my machine without a floppy controller and
it no longer produces traces, just "floppy0: no floppy controllers
found"
Dirk
next prev parent reply other threads:[~2012-01-26 18:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 13:19 Suresh Jayaraman
2012-01-24 22:31 ` Vivek Goyal
2012-01-25 7:59 ` Dirk Gouders
2012-01-25 9:04 ` Dirk Gouders
2012-01-26 15:04 ` Vivek Goyal
2012-01-26 18:05 ` Tejun Heo
2012-01-26 18:53 ` Dirk Gouders [this message]
2012-01-26 19:37 ` Vivek Goyal
2012-01-26 21:48 ` Dirk Gouders
2012-01-26 21:56 ` Vivek Goyal
2012-01-27 6:07 ` Suresh Jayaraman
2012-01-27 11:30 ` Dirk Gouders
2012-01-27 19:54 ` Vivek Goyal
2012-01-28 10:53 ` Dirk Gouders
2012-01-29 19:36 ` Tejun Heo
2012-01-30 6:03 ` Suresh Jayaraman
2012-01-27 6:03 ` Suresh Jayaraman
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=gisjj25m98.fsf@mx10.gouders.net \
--to=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=sjayaraman@suse.com \
--cc=tj@kernel.org \
--cc=vgoyal@redhat.com \
/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
Powered by JetHome