All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, dsahern@kernel.org, kuni1840@gmail.com,
	netdev@vger.kernel.org,
	syzbot+71e724675ba3958edb31@syzkaller.appspotmail.com
Subject: Re: [PATCH v1 net] tcp: Fix listen() warning with v4-mapped-v6 address.
Date: Fri, 13 Oct 2023 17:10:24 +0000	[thread overview]
Message-ID: <169721702453.23617.16807645525327344015.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231010013814.70571-1-kuniyu@amazon.com>

Hello:

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

On Mon, 9 Oct 2023 18:38:14 -0700 you wrote:
> syzbot reported a warning [0] introduced by commit c48ef9c4aed3 ("tcp: Fix
> bind() regression for v4-mapped-v6 non-wildcard address.").
> 
> After the cited commit, a v4 socket's address matches the corresponding
> v4-mapped-v6 tb2 in inet_bind2_bucket_match_addr(), not vice versa.
> 
> During X.X.X.X -> ::ffff:X.X.X.X order bind()s, the second bind() uses
> bhash and conflicts properly without checking bhash2 so that we need not
> check if a v4-mapped-v6 sk matches the corresponding v4 address tb2 in
> inet_bind2_bucket_match_addr().  However, the repro shows that we need
> to check that in a no-conflict case.
> 
> [...]

Here is the summary with links:
  - [v1,net] tcp: Fix listen() warning with v4-mapped-v6 address.
    https://git.kernel.org/netdev/net/c/8702cf12e6ba

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-10-13 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  1:38 [PATCH v1 net] tcp: Fix listen() warning with v4-mapped-v6 address Kuniyuki Iwashima
2023-10-13 16:32 ` Eric Dumazet
2023-10-13 17:10 ` 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=169721702453.23617.16807645525327344015.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+71e724675ba3958edb31@syzkaller.appspotmail.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.