From: Stefan Raspl <raspl@linux.vnet.ibm.com>
To: raspl@linux.vnet.ibm.com,
device-mapper development <dm-devel@redhat.com>,
Jens Axboe <jens.axboe@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
heiko.carstens@de.ibm.coms
Subject: Re: Re: [PATCH] Fix Null pointer Exception
Date: Fri, 10 Oct 2008 09:23:00 +0200 [thread overview]
Message-ID: <48EF02D4.1040605@linux.vnet.ibm.com> (raw)
In-Reply-To: <20081009151749.GO23898@agk.fab.redhat.com>
Alasdair G Kergon wrote:
> On Tue, Oct 07, 2008 at 10:18:40PM +0100, Alasdair G Kergon wrote:
>> Meanwhile I will not be applying that patch, though I may take a patch
>> to provide clean diagnostics should a situation like this occur again.
>
> I'm thinking of something like this:
>
>
> From: Alasdair G Kergon <agk@redhat.com>
>
> Detect and report buggy drivers that destroy their request_queue.
>
> Signed-off-by: Alasdair G Kergon <agk@redhat.com>
> Cc: Stefan Raspl <raspl@linux.vnet.ibm.com>
> Cc: Jens Axboe <jens.axboe@oracle.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
>
> ---
> drivers/md/dm-table.c | 24 ++++++++++++++++++++++--
> 1 files changed, 22 insertions(+), 2 deletions(-)
>
> Index: linux-2.6.27-rc8/drivers/md/dm-table.c
> ===================================================================
> --- linux-2.6.27-rc8.orig/drivers/md/dm-table.c 2008-10-09 14:53:35.000000000 +0100
> +++ linux-2.6.27-rc8/drivers/md/dm-table.c 2008-10-09 14:56:26.000000000 +0100
> @@ -478,6 +478,13 @@ void dm_set_device_limits(struct dm_targ
> {
> struct request_queue *q = bdev_get_queue(bdev);
> struct io_restrictions *rs = &ti->limits;
> + char b[BDEVNAME_SIZE];
> +
> + if (unlikely(!q)) {
> + DMWARN("%s: Cannot set limits for nonexistent device %s",
> + dm_device_name(ti->table->md), bdevname(bdev, b));
> + return;
> + }
>
> /*
> * Combine the device limits low.
> @@ -943,7 +950,14 @@ int dm_table_any_congested(struct dm_tab
>
> list_for_each_entry(dd, devices, list) {
> struct request_queue *q = bdev_get_queue(dd->bdev);
> - r |= bdi_congested(&q->backing_dev_info, bdi_bits);
> + char b[BDEVNAME_SIZE];
> +
> + if (likely(q))
> + r |= bdi_congested(&q->backing_dev_info, bdi_bits);
> + else
> + DMWARN_LIMIT("%s: any_congested: nonexistent device %s",
> + dm_device_name(t->md),
> + bdevname(dd->bdev, b));
> }
>
> return r;
> @@ -956,8 +970,14 @@ void dm_table_unplug_all(struct dm_table
>
> list_for_each_entry(dd, devices, list) {
> struct request_queue *q = bdev_get_queue(dd->bdev);
> + char b[BDEVNAME_SIZE];
>
> - blk_unplug(q);
> + if (likely(q))
> + blk_unplug(q);
> + else
> + DMWARN_LIMIT("%s: Cannot unplug nonexistent device %s",
> + dm_device_name(t->md),
> + bdevname(dd->bdev, b));
> }
> }
>
Looks good to me!
Ciao,
Stefan
--
Linux on System z
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführer: Erich Baier
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
prev parent reply other threads:[~2008-10-10 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 15:40 [PATCH] Fix Null pointer Exception Stefan Raspl
2008-09-09 0:21 ` Andrew Morton
2008-09-23 16:56 ` Alasdair G Kergon
2008-09-24 13:17 ` Stefan Raspl
2008-10-07 21:18 ` Alasdair G Kergon
2008-10-09 15:17 ` Alasdair G Kergon
2008-10-10 7:23 ` Stefan Raspl [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=48EF02D4.1040605@linux.vnet.ibm.com \
--to=raspl@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=heiko.carstens@de.ibm.coms \
--cc=jens.axboe@oracle.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