From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Jens <axboe@kernel.dk>,
linux-kernel <linux-kernel@vger.kernel.org>,
Kent <kmo@daterainc.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH] bio-integrity: add "bip_max_vcnt" into struct bio_integrity_payload
Date: Mon, 30 Jun 2014 11:39:14 +0800 [thread overview]
Message-ID: <53B0DBE2.9030300@cn.fujitsu.com> (raw)
In-Reply-To: <yq1fvin9uje.fsf@sermon.lab.mkp.net>
Hi Martin,
On 06/30/2014 07:15 AM, Martin K. Petersen wrote:
>>>>>> "Gu" == Gu Zheng <guz.fnst@cn.fujitsu.com> writes:
>
> [Sorry about the delay. I'm on vacation right now.]
>
> Gu> But it seems that bip_integrity_vecs() will return the wrong number
> Gu> if the bio is not based on any bio_set for some reason(bio->bi_pool
> Gu> == NULL), because in that case, the bip_inline_vecs[0] is malloced
> Gu> directly. So here we add the bip_max_vcnt to record the count of
> Gu> vector slots, and cleanup the function bip_integrity_vecs().
>
> I'm in agreement with your fix.
Thanks.
>
> However, I'm still not sure what the use case is for bios without an
> associated bioset. I do not see any callers that pass in a NULL bioset.
Please refer to bio_kmalloc()--alloc bio via kmalloc.
And IMO, the API(e.g. bio_alloc_bioset) is EXPORT, any guys(including
some out of mainline code, some special drivers) can alloc a bio via
kmalloc without based on associated bioset.
Regards,
Gu
>
next prev parent reply other threads:[~2014-06-30 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 10:12 [RFC PATCH] bio-integrity: add "bip_max_vcnt" into struct bio_integrity_payload Gu Zheng
2014-06-29 23:15 ` Martin K. Petersen
2014-06-30 3:39 ` Gu Zheng [this message]
2014-06-30 15:56 ` Martin K. Petersen
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=53B0DBE2.9030300@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@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 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.