public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
	paulmck@kernel.org, "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	Dmitry Safonov <dima@arista.com>,
	rcu@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: use 2-arg optimal variant of kfree_rcu()
Date: Mon, 5 Dec 2022 18:10:32 +0100	[thread overview]
Message-ID: <Y44mCDh2eweZD74I@pc636> (raw)
In-Reply-To: <CANn89i+8Au1+Wa_F0QGAz2zfA7UYcCF_9a0BqCpdAqMOrNVbsw@mail.gmail.com>

> On Mon, Dec 5, 2022 at 3:59 PM Uladzislau Rezki <urezki@gmail.com> wrote:
> 
> > So it was a typo then. How did you identify that BUG? Simple go through
> > the code? Or some test coverage?
> 
> Code review. I am the TCP maintainer, in case you do not know.
> 
OK, thank you.

--
Uladzislau Rezki

  reply	other threads:[~2022-12-05 17:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02  5:28 [PATCH net-next] tcp: use 2-arg optimal variant of kfree_rcu() Eric Dumazet
2022-12-02  7:44 ` Pavan Chebbi
2022-12-02 16:05 ` Dmitry Safonov
2022-12-02 18:34 ` Paul E. McKenney
2022-12-02 23:49 ` Joel Fernandes
2022-12-03  0:03   ` Paul E. McKenney
2022-12-03  0:12     ` Joel Fernandes
2022-12-03  0:16       ` Joel Fernandes
2022-12-03  0:28         ` Joel Fernandes
2022-12-05 11:09           ` Uladzislau Rezki
2022-12-05 13:23             ` Eric Dumazet
2022-12-05 14:59               ` Uladzislau Rezki
2022-12-05 16:58                 ` Eric Dumazet
2022-12-05 17:10                   ` Uladzislau Rezki [this message]
2022-12-03  5:50 ` 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=Y44mCDh2eweZD74I@pc636 \
    --to=urezki@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dima@arista.com \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    /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