From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
jiri@resnulli.us, liuhangbin@gmail.com, kuba@kernel.org,
netdev@vger.kernel.org, stfomichev@gmail.com,
shannon.nelson@amd.com, darren.kenny@oracle.com
Subject: Re: [PATCH 6.12.y 0/2] Fix rtnetlink.sh kselftest failures in stable
Date: Thu, 13 Feb 2025 15:51:09 +0100 [thread overview]
Message-ID: <2025021346-lankiness-vagabond-60d5@gregkh> (raw)
In-Reply-To: <a33f888c-2121-46c0-8fcb-7ba469309a8b@oracle.com>
On Thu, Feb 13, 2025 at 08:14:25PM +0530, Harshit Mogalapalli wrote:
> Hi Greg,
>
> On 09/02/25 00:25, Harshit Mogalapalli wrote:
> > This is reproducible on on stable kernels after the backport of commit:
> > 2cf567f421db ("netdevsim: copy addresses for both in and out paths") to
> > stable kernels.
> >
> > Using a single cover letter for all stable kernels but will send
> ...
> > Solution:
> > ========
> >
> > Backport both the commits commit: c71bc6da6198 ("netdevsim: print human
> > readable IP address") and script fixup commit: 3ec920bb978c ("selftests:
> > rtnetlink: update netdevsim ipsec output format") to all stable kernels
> > which have commit: 2cf567f421db ("netdevsim: copy addresses for both in
> > and out paths") in them.
> >
> > Another clue to say this is right way to do this is that these above
> > three patches did go as patchset into net/ [1].
> >
> > I am sending patches for all stable trees differently, however I am
> > using same cover letter.
> >
> > Tested all stable kernels after patching. This failure is no more
> > reproducible.
> >
>
> Ping on this series:
>
> 6.12.y: https://lore.kernel.org/all/20250208185521.2998155-1-harshit.m.mogalapalli@oracle.com/
>
> 6.6.y: https://lore.kernel.org/all/20250208185711.2998210-1-harshit.m.mogalapalli@oracle.com/
>
> 6.1.y: https://lore.kernel.org/all/20250208185756.2998240-1-harshit.m.mogalapalli@oracle.com/
>
> 5.15.y: https://lore.kernel.org/all/20250208185909.2998264-1-harshit.m.mogalapalli@oracle.com/
>
> 5.10.y: https://lore.kernel.org/all/20250208190215.2998554-1-harshit.m.mogalapalli@oracle.com/
>
> I noticed new stable rc tags being released, so pinging. Sorry if I pinged
> before you got to these.
No, thanks for the ping, these fell through the cracks, I'll queue them
up for the next round after these.
thanks,
greg k-h
prev parent reply other threads:[~2025-02-13 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 18:55 [PATCH 6.12.y 0/2] Fix rtnetlink.sh kselftest failures in stable Harshit Mogalapalli
2025-02-08 18:55 ` [PATCH 6.12.y 1/2] netdevsim: print human readable IP address Harshit Mogalapalli
2025-02-08 18:55 ` [PATCH 6.12.y 2/2] selftests: rtnetlink: update netdevsim ipsec output format Harshit Mogalapalli
2025-02-13 14:44 ` [PATCH 6.12.y 0/2] Fix rtnetlink.sh kselftest failures in stable Harshit Mogalapalli
2025-02-13 14:51 ` Greg Kroah-Hartman [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=2025021346-lankiness-vagabond-60d5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=darren.kenny@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=shannon.nelson@amd.com \
--cc=stable@vger.kernel.org \
--cc=stfomichev@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox