From: Sasha Levin <sashal@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, gregkh@linuxfoundation.org,
stable@vger.kernel.org
Subject: Re: [PATCH -stable,4.14 0/8] more stable fixes for 4.14
Date: Mon, 22 May 2023 13:55:44 -0400 [thread overview]
Message-ID: <ZGusoFuQqgzDWXAx@sashalap> (raw)
In-Reply-To: <20230516151606.4892-1-pablo@netfilter.org>
On Tue, May 16, 2023 at 05:15:58PM +0200, Pablo Neira Ayuso wrote:
>Hi Greg, Sasha,
>
>This is second round of -stable backport fixes for 4.14. This batch
>includes dependency patches which are not currently in the 4.14 branch.
>
>The following list shows the backported patches, I am using original
>commit IDs for reference:
>
>1) 08a01c11a5bb ("netfilter: nftables: statify nft_parse_register()")
>
>2) 6e1acfa387b9 ("netfilter: nf_tables: validate registers coming from userspace.")
>
>3) 20a1452c3542 ("netfilter: nf_tables: add nft_setelem_parse_key()")
>
>4) fdb9c405e35b ("netfilter: nf_tables: allow up to 64 bytes in the set element data area")
>
>5) 7e6bc1f6cabc ("netfilter: nf_tables: stricter validation of element data")
>
>6) 215a31f19ded ("netfilter: nft_dynset: do not reject set updates with NFT_SET_EVAL")
>
>7) 36d5b2913219 ("netfilter: nf_tables: do not allow RULE_ID to refer to another chain")
>
>8) 470ee20e069a ("netfilter: nf_tables: do not allow SET_ID to refer to another table")
I've applied the 5.4 and 4.19 series, but it looks like patch #1 here
fails to apply. Could you please re-send the 4.14 series?
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-05-22 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 15:15 [PATCH -stable,4.14 0/8] more stable fixes for 4.14 Pablo Neira Ayuso
2023-05-16 15:15 ` [PATCH -stable,4.14 1/8] netfilter: nftables: statify nft_parse_register() Pablo Neira Ayuso
2023-05-16 15:16 ` [PATCH -stable,4.14 2/8] netfilter: nf_tables: validate registers coming from userspace Pablo Neira Ayuso
2023-05-16 15:16 ` [PATCH -stable,4.14 3/8] netfilter: nf_tables: add nft_setelem_parse_key() Pablo Neira Ayuso
2023-05-16 15:16 ` [PATCH -stable,4.14 4/8] netfilter: nf_tables: allow up to 64 bytes in the set element data area Pablo Neira Ayuso
2023-05-16 15:16 ` [PATCH -stable,4.14 5/8] netfilter: nf_tables: stricter validation of element data Pablo Neira Ayuso
2023-05-16 15:16 ` [PATCH -stable,4.14 6/8] netfilter: nft_dynset: do not reject set updates with NFT_SET_EVAL Pablo Neira Ayuso
2023-05-16 15:16 ` [PATCH -stable,4.14 7/8] netfilter: nf_tables: do not allow RULE_ID to refer to another chain Pablo Neira Ayuso
2023-05-16 15:16 ` [PATCH -stable,4.14 8/8] netfilter: nf_tables: do not allow SET_ID to refer to another table Pablo Neira Ayuso
2023-05-22 17:55 ` Sasha Levin [this message]
2023-05-23 8:41 ` [PATCH -stable,4.14 0/8] more stable fixes for 4.14 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=ZGusoFuQqgzDWXAx@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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