From: "Matias Bjørling" <m@bjorling.me>
To: Thiago Farina <tfransosi@gmail.com>
Cc: linux-block@vger.kernel.org,
linux list <linux-kernel@vger.kernel.org>,
axboe@fb.com, geert@linux-m68k.org
Subject: Re: [PATCH] lightnvm: change max_phys_sect to ushort
Date: Mon, 16 Nov 2015 12:21:50 +0100 [thread overview]
Message-ID: <5649BC4E.7000105@bjorling.me> (raw)
In-Reply-To: <CACnwZYejgm-n80FH8yxtZn15_HDgMjL4tB89os+MO4oVzgL2GA@mail.gmail.com>
On 11/16/2015 12:18 PM, Thiago Farina wrote:
> On Thu, Nov 12, 2015 at 4:35 PM, Matias Bjørling <m@bjorling.me> wrote:
>> The max_phys_sect variable is defined as a char. We do a boundary check
>> to maximally allow 256 physical page descriptors per command. As we are
>> not indexing from zero. This expression is always in false. Bump the
>> max_phys_sect to an unsigned short to support the range check.
>>
> You might have to change the commit message to match the code change.
> s/unsigned short/unsigned int. RIght?
You're right. It has been fixed.
>
>> Signed-off-by: Matias Bjørling <m@bjorling.me>
>> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
>> ---
>> include/linux/lightnvm.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/linux/lightnvm.h b/include/linux/lightnvm.h
>> index 69c9057..4b1cd3d 100644
>> --- a/include/linux/lightnvm.h
>> +++ b/include/linux/lightnvm.h
>> @@ -220,7 +220,7 @@ struct nvm_dev_ops {
>> nvm_dev_dma_alloc_fn *dev_dma_alloc;
>> nvm_dev_dma_free_fn *dev_dma_free;
>>
>> - uint8_t max_phys_sect;
>> + unsigned int max_phys_sect;
>> };
>>
>> struct nvm_lun {
>
>
prev parent reply other threads:[~2015-11-16 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 18:35 [PATCH] lightnvm: change max_phys_sect to ushort Matias Bjørling
2015-11-12 18:42 ` Geert Uytterhoeven
2015-11-12 18:57 ` Matias Bjørling
2015-11-12 19:02 ` Linus Torvalds
2015-11-12 19:05 ` Matias Bjørling
2015-11-16 11:18 ` Thiago Farina
2015-11-16 11:21 ` Matias Bjørling [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=5649BC4E.7000105@bjorling.me \
--to=m@bjorling.me \
--cc=axboe@fb.com \
--cc=geert@linux-m68k.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tfransosi@gmail.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.