From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"David Woodhouse" <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: nand: Fix memory allocation in nanddev_bbt_init()
Date: Wed, 28 Nov 2018 14:55:45 +0000 [thread overview]
Message-ID: <7634bb45-6167-31e8-e169-b5c9bf7e2fc5@kontron.de> (raw)
In-Reply-To: <20181128154104.577d5923@bbrezillon>
Hi Boris,
On 28.11.18 15:41, Boris Brezillon wrote:
> On Tue, 27 Nov 2018 07:44:52 +0000
> Schrempf Frieder <frieder.schrempf@kontron.de> wrote:
>
>> Fix the size of the buffer allocated to store the in-memory BBT.
>> This bug was previously hidden by a different bug, that was fixed in
>> d098093ba06e.
>>
>> Fixes: 9c3736a3de21 ("mtd: nand: Add core infrastructure to deal with NAND devices")
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
>
> Looks like your From header does not match the SoB tag
> ('Frieder Schrempf' vs 'Schrempf Frieder') and checkpatch does not like
> that. I'll fix it when applying, but maybe you should fix
> your .gitconfig to make them match.
Actually the From header in my local patch is correct (<first name>
<last name>, Frieder Schrempf) as it comes from my git config. But since
our company was renamed and our mail servers were transferred, our
e-mails are sent with From=<last name> <first name>.
It seems like git send-email or patchwork or whatever uses the
information from the e-mail header instead of what is in the patch.
I will try to raise this issue with our IT department as this would be
best fixed on their side.
Thanks,
Frieder
>
>> ---
>> drivers/mtd/nand/bbt.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/mtd/nand/bbt.c b/drivers/mtd/nand/bbt.c
>> index 56cde38..c12497f 100644
>> --- a/drivers/mtd/nand/bbt.c
>> +++ b/drivers/mtd/nand/bbt.c
>> @@ -27,7 +27,8 @@ int nanddev_bbt_init(struct nand_device *nand)
>> unsigned int nwords = DIV_ROUND_UP(nblocks * bits_per_block,
>> BITS_PER_LONG);
>>
>> - nand->bbt.cache = kzalloc(nwords, GFP_KERNEL);
>> + nand->bbt.cache = kzalloc(nwords * (BITS_PER_LONG / BITS_PER_BYTE),
>> + GFP_KERNEL);
>> if (!nand->bbt.cache)
>> return -ENOMEM;
>>
>
next prev parent reply other threads:[~2018-11-28 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 7:44 Schrempf Frieder
2018-11-27 8:22 ` Boris Brezillon
2018-11-27 8:30 ` Schrempf Frieder
2018-11-27 9:27 ` Miquel Raynal
2018-11-28 14:41 ` Boris Brezillon
2018-11-28 14:55 ` Schrempf Frieder [this message]
2018-11-28 15:02 ` Boris Brezillon
2018-11-28 15:19 ` Schrempf Frieder
2018-11-28 15:28 ` Boris Brezillon
2018-11-29 18:11 ` Schrempf Frieder
2018-11-30 9:37 ` Boris Brezillon
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=7634bb45-6167-31e8-e169-b5c9bf7e2fc5@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®