From: Jean-Jacques Hiblot <jjhiblot@traphandler.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: <lee.jones@linaro.org>, <pavel@ucw.cz>, <robh+dt@kernel.org>,
<sven.schwermer@disruptive-technologies.com>,
<krzysztof.kozlowski+dt@linaro.org>, <johan+linaro@kernel.org>,
<marijn.suijten@somainline.org>, <bjorn.andersson@linaro.org>,
<jacek.anaszewski@gmail.com>, <linux-leds@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/6] devres: provide devm_krealloc_array()
Date: Fri, 14 Oct 2022 11:17:06 +0200 [thread overview]
Message-ID: <fb513ce8-3c2a-6b67-7abe-1d5671b682d0@traphandler.com> (raw)
In-Reply-To: <CAHp75VcX2w9mdzbKtfRpc-4zrz8tp33Q5uHyBfds8MJfyeVYvQ@mail.gmail.com>
On 07/10/2022 18:18, Andy Shevchenko wrote:
>> {
>> return devm_kmalloc_array(dev, n, size, flags | __GFP_ZERO);
>> }
> Missed blank line?
There is no blank line after the definitions of devm_kzalloc(),
devm_kmalloc_array() and devm_kcalloc() defined just above.
>
>> +static inline void *devm_krealloc_array(struct device *dev,
>> + void *p,
>> + size_t new_n,
>> + size_t new_size,
>> + gfp_t flags)
>> +{
>> + size_t bytes;
>> +
>> + if (unlikely(check_mul_overflow(new_n, new_size, &bytes)))
>> + return NULL;
> I'm not sure it is what we want, but I have read the man realloc and found this:
>
> ... reallocarray() fails safely in the case where the multiplication
> would overflow. If such an overflow occurs, reallocarray() returns NULL,
> sets errno to ENOMEM, and leaves the original block of memory
> unchanged.
>
> So, perhaps you can add that this behaviour mimics reallocarray()?
except for the errno part, that is what is does. I don't think we should
use ERR_PTR in this case as the other allocation functions don't use it.
>
>> + return devm_krealloc(dev, p, bytes, flags);
>> +}
> ...
>
> All comments are minor, feel free to add
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
>
next prev parent reply other threads:[~2022-10-14 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 14:56 [PATCH v4 0/6] Add a multicolor LED driver for groups of monochromatic LEDs Jean-Jacques Hiblot
2022-10-07 14:56 ` [PATCH v4 1/6] devres: provide devm_krealloc_array() Jean-Jacques Hiblot
2022-10-07 16:18 ` Andy Shevchenko
2022-10-14 9:17 ` Jean-Jacques Hiblot [this message]
2022-10-07 14:56 ` [PATCH v4 2/6] leds: class: simplify the implementation of devm_of_led_get() Jean-Jacques Hiblot
2022-10-07 14:56 ` [PATCH v4 3/6] leds: provide devm_of_led_get_optional() Jean-Jacques Hiblot
2022-10-07 16:24 ` Andy Shevchenko
2022-10-07 14:56 ` [PATCH v4 4/6] leds: class: store the color index in struct led_classdev Jean-Jacques Hiblot
2022-10-07 16:26 ` Andy Shevchenko
2022-10-07 14:56 ` [PATCH v4 5/6] dt-bindings: leds: Add binding for a multicolor group of LEDs Jean-Jacques Hiblot
2022-10-07 14:56 ` [PATCH v4 6/6] leds: Add a multicolor LED driver to group monochromatic LEDs Jean-Jacques Hiblot
2022-10-07 16:31 ` Andy Shevchenko
2022-10-14 9:15 ` Jean-Jacques Hiblot
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=fb513ce8-3c2a-6b67-7abe-1d5671b682d0@traphandler.com \
--to=jjhiblot@traphandler.com \
--cc=andy.shevchenko@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=johan+linaro@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=sven.schwermer@disruptive-technologies.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 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®