From: patchwork-bot+netdevbpf@kernel.org
To: Zijian Zhang <zijianzhang@bytedance.com>
Cc: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com,
cong.wang@bytedance.com, xiaochun.lu@bytedance.com
Subject: Re: [PATCH net 0/2] fix OOM and order check in msg_zerocopy selftest
Date: Thu, 04 Jul 2024 02:50:31 +0000 [thread overview]
Message-ID: <172006143116.17004.3259340660154985124.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240701225349.3395580-1-zijianzhang@bytedance.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 1 Jul 2024 22:53:47 +0000 you wrote:
> From: Zijian Zhang <zijianzhang@bytedance.com>
>
> In selftests/net/msg_zerocopy.c, it has a while loop keeps calling sendmsg
> on a socket with MSG_ZEROCOPY flag, and it will recv the notifications
> until the socket is not writable. Typically, it will start the receiving
> process after around 30+ sendmsgs. However, as the introduction of commit
> dfa2f0483360 ("tcp: get rid of sysctl_tcp_adv_win_scale"), the sender is
> always writable and does not get any chance to run recv notifications.
> The selftest always exits with OUT_OF_MEMORY because the memory used by
> opt_skb exceeds the net.core.optmem_max. Meanwhile, it could be set to a
> different value to trigger OOM on older kernels too.
>
> [...]
Here is the summary with links:
- [net,1/2] selftests: fix OOM in msg_zerocopy selftest
https://git.kernel.org/netdev/net/c/af2b7e5b741a
- [net,2/2] selftests: make order checking verbose in msg_zerocopy selftest
https://git.kernel.org/netdev/net/c/7d6d8f0c8b70
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-04 2:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 22:53 [PATCH net 0/2] fix OOM and order check in msg_zerocopy selftest zijianzhang
2024-07-01 22:53 ` [PATCH net 1/2] selftests: fix OOM " zijianzhang
2024-07-02 13:17 ` Willem de Bruijn
2024-07-04 1:50 ` Jakub Kicinski
2024-07-04 2:32 ` Zijian Zhang
2024-07-04 2:42 ` Jakub Kicinski
2024-07-01 22:53 ` [PATCH net 2/2] selftests: make order checking verbose " zijianzhang
2024-07-02 13:18 ` Willem de Bruijn
2024-07-02 18:05 ` Zijian Zhang
2024-07-04 2:50 ` patchwork-bot+netdevbpf [this message]
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=172006143116.17004.3259340660154985124.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xiaochun.lu@bytedance.com \
--cc=zijianzhang@bytedance.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).