All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Llamas <cmllamas@google.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, netdev <netdev@vger.kernel.org>,
	liuwei.a@oppo.com
Subject: Re: [PATCH net] inet: fully convert sk->sk_rx_dst to RCU rules
Date: Thu, 20 Oct 2022 22:55:39 +0000	[thread overview]
Message-ID: <Y1HR61VKKNFRv/X9@google.com> (raw)
In-Reply-To: <CANn89iJsZsmw9+RryFzMhEBqdqUMD=LRkJZ85k1ksdAzypfefg@mail.gmail.com>

On Thu, Oct 20, 2022 at 02:53:06PM -0700, Eric Dumazet wrote:
> On Thu, Oct 20, 2022 at 2:05 PM Carlos Llamas <cmllamas@google.com> wrote:
> >
> > On Mon, Dec 20, 2021 at 06:33:30AM -0800, Eric Dumazet wrote:
> 
> >
> > Eric, this patch was picked for v5.15 stable and I wonder whether this
> > needs to be backported to older branches too. The Fixes commit quoted
> > here seems to go back all the way to v3.5. Would you know?
> 
> I guess nobody cared to address some merge conflicts on older kernel versions.
> 
> If you want, you could handle the backport, this patch can help some
> rare race windows
> on preemptable kernels.

Sounds good, I'll have a look at backporting this patch.

      reply	other threads:[~2022-10-20 22:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 14:33 [PATCH net] inet: fully convert sk->sk_rx_dst to RCU rules Eric Dumazet
2021-12-21  3:10 ` patchwork-bot+netdevbpf
2022-10-20 21:05 ` Carlos Llamas
2022-10-20 21:53   ` Eric Dumazet
2022-10-20 22:55     ` Carlos Llamas [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=Y1HR61VKKNFRv/X9@google.com \
    --to=cmllamas@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=liuwei.a@oppo.com \
    --cc=netdev@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 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.