From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: netfilter-devel@vger.kernel.org,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: Testing stable backports for netfilter
Date: Mon, 10 Jun 2024 23:59:57 +0200 [thread overview]
Message-ID: <Zmd3XaiC_GiCakyf@calendula> (raw)
In-Reply-To: <652cad2e-2857-4374-a597-a3337f9330f0@oracle.com>
On Mon, Jun 10, 2024 at 11:51:53PM +0530, Harshit Mogalapalli wrote:
> Hello netfilter developers,
>
> Do we have any tests that we could run before sending a stable backport in
> netfilter/ subsystem to stable@vger ?
>
> Let us say we have a CVE fix which is only backported till 5.10.y but it is
> needed is 5.4.y and 4.19.y, the backport might need to easy to make, just
> fixing some conflicts due to contextual changes or missing commits.
Which one in particular is missing?
> One question that comes in my mind is did I test that particular code, often
> testing that particular code is tough unless the reproducer is public. So I
> thought it would be good to learn about any netfilter test suite(set of
> tests) to run before sending a backport to stable kernel which might ensure
> we don't introduce regressions.
There is tests/shell under the nftables userspace tree, it also
detected the features that are available in your kernel.
next prev parent reply other threads:[~2024-06-10 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 18:21 Testing stable backports for netfilter Harshit Mogalapalli
2024-06-10 21:59 ` Pablo Neira Ayuso [this message]
2024-06-11 5:58 ` Harshit Mogalapalli
2024-06-11 8:41 ` Pablo Neira Ayuso
2024-06-11 8:59 ` Vegard Nossum
2024-06-11 9:00 ` Pablo Neira Ayuso
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=Zmd3XaiC_GiCakyf@calendula \
--to=pablo@netfilter.org \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=vegard.nossum@oracle.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;
as well as URLs for NNTP newsgroup(s).