From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <pablo@netfilter.org>, <kadlec@netfilter.org>, <roopa@nvidia.com>,
<razor@blackwall.org>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<dsahern@kernel.org>, <krzk@kernel.org>,
<netfilter-devel@vger.kernel.org>, <coreteam@netfilter.org>,
<bridge@lists.linux.dev>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next 0/5] net: Use kmemdup_array() instead of kmemdup() for multiple allocation
Date: Wed, 28 Aug 2024 15:07:18 +0800 [thread overview]
Message-ID: <9f8e0482-0521-a4e2-45f9-256b42927d06@huawei.com> (raw)
In-Reply-To: <20240828071004.1245213-1-ruanjinjie@huawei.com>
Please ignore this email, didn't notice there was already a patch for this
On 2024/8/28 15:09, Jinjie Ruan wrote:
> Let the kmemdup_array() take care about multiplication and possible
> overflows.
>
> Jinjie Ruan (5):
> nfc: core: Use kmemdup_array() instead of kmemdup() for multiple
> allocation
> netfilter: Use kmemdup_array() instead of kmemdup() for multiple
> allocation
> netfilter: arptables: Use kmemdup_array() instead of kmemdup() for
> multiple allocation
> netfilter: iptables: Use kmemdup_array() instead of kmemdup() for
> multiple allocation
> netfilter: nf_nat: Use kmemdup_array() instead of kmemdup() for
> multiple allocation
>
> net/bridge/netfilter/ebtables.c | 2 +-
> net/ipv4/netfilter/arp_tables.c | 2 +-
> net/ipv4/netfilter/ip_tables.c | 2 +-
> net/netfilter/nf_nat_core.c | 2 +-
> net/nfc/core.c | 5 ++---
> 5 files changed, 6 insertions(+), 7 deletions(-)
>
next prev parent reply other threads:[~2024-08-28 7:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 7:09 [PATCH -next 0/5] net: Use kmemdup_array() instead of kmemdup() for multiple allocation Jinjie Ruan
2024-08-28 7:07 ` Jinjie Ruan [this message]
2024-08-28 7:10 ` [PATCH -next 1/5] nfc: core: " Jinjie Ruan
2024-08-28 7:10 ` [PATCH -next 2/5] netfilter: " Jinjie Ruan
2024-08-28 7:10 ` [PATCH -next 3/5] netfilter: arptables: " Jinjie Ruan
2024-08-28 7:10 ` [PATCH -next 4/5] netfilter: iptables: " Jinjie Ruan
2024-08-28 8:42 ` Pablo Neira Ayuso
2024-08-28 14:51 ` Pablo Neira Ayuso
2024-08-28 7:10 ` [PATCH -next 5/5] netfilter: nf_nat: " Jinjie Ruan
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=9f8e0482-0521-a4e2-45f9-256b42927d06@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=bridge@lists.linux.dev \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kadlec@netfilter.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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