All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, jiri@resnulli.us, j.vosburgh@gmail.com,
	andy@greyhouse.net, netdev@vger.kernel.org, jarod@redhat.com,
	razor@blackwall.org, simon.horman@corigine.com,
	wangyufen@huawei.com,
	syzbot+60748c96cf5c6df8e581@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2] net: fix stack overflow when LRO is disabled for virtual interfaces
Date: Sat, 20 May 2023 05:50:19 +0000	[thread overview]
Message-ID: <168456181968.1665.6469597610813083931.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230517143010.3596250-1-ap420073@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 17 May 2023 14:30:10 +0000 you wrote:
> When the virtual interface's feature is updated, it synchronizes the
> updated feature for its own lower interface.
> This propagation logic should be worked as the iteration, not recursively.
> But it works recursively due to the netdev notification unexpectedly.
> This problem occurs when it disables LRO only for the team and bonding
> interface type.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: fix stack overflow when LRO is disabled for virtual interfaces
    https://git.kernel.org/netdev/net/c/ae9b15fbe634

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-05-20  5:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 14:30 [PATCH net v2] net: fix stack overflow when LRO is disabled for virtual interfaces Taehee Yoo
2023-05-17 14:59 ` Eric Dumazet
2023-05-17 15:02 ` Nikolay Aleksandrov
2023-05-17 16:15 ` Jakub Kicinski
2023-05-17 17:28   ` Taehee Yoo
2023-05-17 18:45     ` Jakub Kicinski
2023-05-19  6:25       ` Taehee Yoo
2023-05-19 21:31         ` Jakub Kicinski
2023-05-20  5: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=168456181968.1665.6469597610813083931.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andy@greyhouse.net \
    --cc=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=j.vosburgh@gmail.com \
    --cc=jarod@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=simon.horman@corigine.com \
    --cc=syzbot+60748c96cf5c6df8e581@syzkaller.appspotmail.com \
    --cc=wangyufen@huawei.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.