From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <geliang@kernel.org>
Cc: <davem@davemloft.net>, <dsahern@kernel.org>,
<edumazet@google.com>, <horms@kernel.org>, <kuba@kernel.org>,
<kuniyu@amazon.com>, <linux-sctp@vger.kernel.org>,
<lucien.xin@gmail.com>, <marcelo.leitner@gmail.com>,
<martineau@kernel.org>, <matttbe@kernel.org>,
<mptcp@lists.linux.dev>, <ncardwell@google.com>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<tanggeliang@kylinos.cn>, <willemb@google.com>
Subject: Re: [PATCH net-next v2 2/3] net: use sock_kmemdup for ip_options
Date: Mon, 3 Mar 2025 15:18:26 -0800 [thread overview]
Message-ID: <20250303231826.52654-1-kuniyu@amazon.com> (raw)
In-Reply-To: <91ae749d66600ec6fb679e0e518fda6acb5c3e6f.1740735165.git.tanggeliang@kylinos.cn>
From: Geliang Tang <geliang@kernel.org>
Date: Fri, 28 Feb 2025 18:01:32 +0800
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Instead of using sock_kmalloc() to allocate an ip_options and then
> immediately duplicate another ip_options to the newly allocated one in
> ipv6_dup_options(), mptcp_copy_ip_options() and sctp_v4_copy_ip_options(),
> the newly added sock_kmemdup() helper can be used to simplify the code.
>
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
next prev parent reply other threads:[~2025-03-03 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 10:01 [PATCH net-next v2 0/3] add sock_kmemdup helper Geliang Tang
2025-02-28 10:01 ` [PATCH net-next v2 1/3] sock: " Geliang Tang
2025-03-03 23:16 ` Kuniyuki Iwashima
2025-02-28 10:01 ` [PATCH net-next v2 2/3] net: use sock_kmemdup for ip_options Geliang Tang
2025-03-03 23:18 ` Kuniyuki Iwashima [this message]
2025-02-28 10:01 ` [PATCH net-next v2 3/3] mptcp: use sock_kmemdup for address entry Geliang Tang
2025-02-28 11:08 ` [PATCH net-next v2 0/3] add sock_kmemdup helper MPTCP CI
2025-02-28 12:06 ` Matthieu Baerts
2025-03-04 2:10 ` patchwork-bot+netdevbpf
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=20250303231826.52654-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tanggeliang@kylinos.cn \
--cc=willemb@google.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.