Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Jiayuan Chen <jiayuan.chen@shopee.com>, 1135514@bugs.debian.org
Cc: Paolo Abeni <pabeni@redhat.com>, Sasha Levin <sashal@kernel.org>,
	regressions@lists.linux.dev, stable@vger.kernel.org,
	podorski <podorski@gmail.com>,
	Brad Barnett <debian-bugs5@l8r.net>,
	"David S. Miller" <davem@davemloft.net>,
	David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>
Subject: Re: Bug#1135514: [6.1.y regresssion] 9a95ec9144ee ("xfrm: fix ip_rt_bug race in icmp_route_lookup reverse path") causes log spam on ping to unreachable host
Date: Wed, 6 May 2026 11:39:29 +0200	[thread overview]
Message-ID: <afsMUZa99G_gsve1@eldamar.lan> (raw)
In-Reply-To: <CAL3Ev5070_=K9F9+03GrE2+4tgr=j_CO19=m4ZPTd17YSwmokQ@mail.gmail.com>

Hi Jiayuan,

On Wed, May 06, 2026 at 09:04:24AM +0800, Jiayuan Chen wrote:
> I think it because we failed to backport  this patch before:
> https://lore.kernel.org/stable/20250207161555-b1a8749027831a1a@stable.kernel.org/T/#m0c880c1f04f7211aea9b7f6b4de0b64aa1726417

Which won't apply cleanly, I assume this was the reason it got not
backported to 6.1.y. Do you have a backport of that, or should the
original commit introducing the issue be reverted from 6.1.y?

Regards,
Salvtore

  reply	other threads:[~2026-05-06  9:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-02  9:22 [6.1.y regresssion] 9a95ec9144ee ("xfrm: fix ip_rt_bug race in icmp_route_lookup reverse path") causes log spam on ping to unreachable host Salvatore Bonaccorso
2026-05-06  1:04 ` Jiayuan Chen
2026-05-06  9:39   ` Salvatore Bonaccorso [this message]
2026-05-06  9:47     ` Bug#1135514: " Jiayuan Chen
2026-05-06 12:00       ` Salvatore Bonaccorso

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=afsMUZa99G_gsve1@eldamar.lan \
    --to=carnil@debian.org \
    --cc=1135514@bugs.debian.org \
    --cc=davem@davemloft.net \
    --cc=debian-bugs5@l8r.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jiayuan.chen@shopee.com \
    --cc=kuba@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=podorski@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@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