[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161012074307.GB5687@mwanda>
Date: Wed, 12 Oct 2016 11:28:39 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Jes Sorensen <Jes.Sorensen@...hat.com>
Cc: Richard Weinberger <richard.weinberger@...il.com>,
SF Markus Elfring <elfring@...rs.sourceforge.net>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
Christoph Hellwig <hch@....de>,
Guoqing Jiang <gqjiang@...e.com>, Jens Axboe <axboe@...com>,
Mike Christie <mchristi@...hat.com>,
Neil Brown <neilb@...e.com>, Shaohua Li <shli@...nel.org>,
Tomasz Majchrzak <tomasz.majchrzak@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
Julia Lawall <julia.lawall@...6.fr>
Subject: Re: [PATCH 24/54] md/raid1: Improve another size determination in
setup_conf()
Compare:
foo = kmalloc(sizeof(*foo), GFP_KERNEL);
This says you are allocating enough space for foo. It can be reviewed
by looking at one line. If you change the type of foo it will still
work.
foo = kmalloc(sizeof(struct whatever), GFP_KERNEL);
There isn't enough information to say if this is correct. If you change
the type of foo then you have to update the allocation as well.
It's not a super common type of bug, but I see it occasionally.
regards,
dan carpenter
Powered by blists - more mailing lists