From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Kuniyuki Iwashima <kuniyu@amazon.com>,
Kuniyuki Iwashima <kuni1840@gmail.com>, <netdev@vger.kernel.org>
Subject: [PATCH v3 net 0/2] sk->sk_forward_alloc fixes.
Date: Thu, 9 Feb 2023 16:22:00 -0800 [thread overview]
Message-ID: <20230210002202.81442-1-kuniyu@amazon.com> (raw)
The first patch fixes a negative sk_forward_alloc by adding
sk_rmem_schedule() before skb_set_owner_r(), and second patch
removes an unnecessary WARN_ON_ONCE().
Changes:
v3:
* Factorise a common pattern in Patch 1 as suggested by Eric
v2: https://lore.kernel.org/netdev/20230209013329.87879-1-kuniyu@amazon.com/
* Add the first patch
v1: https://lore.kernel.org/netdev/20230207183718.54520-1-kuniyu@amazon.com/
Kuniyuki Iwashima (2):
dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions.
net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from
sk_stream_kill_queues().
include/net/sock.h | 13 +++++++++++++
net/caif/caif_socket.c | 1 +
net/core/stream.c | 1 -
net/dccp/ipv6.c | 7 ++-----
net/ipv6/tcp_ipv6.c | 10 +++-------
5 files changed, 19 insertions(+), 13 deletions(-)
--
2.30.2
next reply other threads:[~2023-02-10 0:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 0:22 Kuniyuki Iwashima [this message]
2023-02-10 0:22 ` [PATCH v3 net 1/2] dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions Kuniyuki Iwashima
2023-02-10 14:12 ` Eric Dumazet
2023-02-27 0:17 ` Hauke Mehrtens
2023-02-27 0:36 ` Kuniyuki Iwashima
2023-02-10 0:22 ` [PATCH v3 net 2/2] net: Remove WARN_ON_ONCE(sk->sk_forward_alloc) from sk_stream_kill_queues() Kuniyuki Iwashima
2023-02-10 14:13 ` Eric Dumazet
2023-02-11 4:10 ` [PATCH v3 net 0/2] sk->sk_forward_alloc fixes 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=20230210002202.81442-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).