From: Junichi Nomura <j-nomura@ce.jp.nec.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm: Fix oops when clone_and_map_rq returns !DM_MAPIO_REMAPPED
Date: Wed, 27 May 2015 22:48:15 +0000 [thread overview]
Message-ID: <556649AF.4050303@ce.jp.nec.com> (raw)
In-Reply-To: <20150527135012.GB16050@redhat.com>
On 05/27/15 22:50, Mike Snitzer wrote:
>> Hi Junichi,
>>
>> In reviewing this patch I wondered if it better to xplicitly check for a
>> return of DM_MAPIO_REQUEUE in map_request() since that is the only other
>> return that is possible. I'm still on the fence but your patch is more
>> conservative and at least we won't go on to try to setup_clone, etc if
>> for some reason in the future a new DM_MAPIO_* were invented and
>> returned from clone_and_map_rq().
Either way should work. But I wanted to make it explicit
to call setup_clone() only when DM_MAPIO_REMAPPED is returned.
>> I do intend to revise the header slightly to make explicit references to
>> function names in some places to improve clarity. I'll have to double
>> check but I _think_ this should cc stable@ too since blk-mq support was
>> added in Linux 4.0 (IIRC).
>
> FYI, here is the revised header:
> https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.1&id=3a1407559a593d4360af12dd2df5296bf8eb0d28
Thanks for the nice revision.
--
Jun'ichi Nomura, NEC Corporation
prev parent reply other threads:[~2015-05-27 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 4:22 [PATCH] dm: Fix oops when clone_and_map_rq returns !DM_MAPIO_REMAPPED Junichi Nomura
2015-05-27 13:22 ` Mike Snitzer
2015-05-27 13:50 ` Mike Snitzer
2015-05-27 22:48 ` Junichi Nomura [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=556649AF.4050303@ce.jp.nec.com \
--to=j-nomura@ce.jp.nec.com \
--cc=dm-devel@redhat.com \
--cc=snitzer@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 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.