From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, Stefano Brivio <sbrivio@redhat.com>
Subject: Re: [PATCH nf] netfilter: nft_set_pipapo: fix out of memory error handling
Date: Wed, 23 Aug 2023 11:10:54 +0200 [thread overview]
Message-ID: <ZOXNHp3U5o1pSTno@calendula> (raw)
In-Reply-To: <20230823072752.16361-1-fw@strlen.de>
On Wed, Aug 23, 2023 at 09:27:47AM +0200, Florian Westphal wrote:
> Several instances of pipapo_resize() don't propagate allocation failures,
> this causes a crash when fault injection is used with
>
> echo Y > /sys/kernel/debug/failslab/ignore-gfp-wait
>
> Cc: Stefano Brivio <sbrivio@redhat.com>
Fixes: 3c4287f62044 ("nf_tables: Add set type for arbitrary concatenation of ranges")
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
> net/netfilter/nft_set_pipapo.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/net/netfilter/nft_set_pipapo.c b/net/netfilter/nft_set_pipapo.c
> index 3757fcc55723..6af9c9ed4b5c 100644
> --- a/net/netfilter/nft_set_pipapo.c
> +++ b/net/netfilter/nft_set_pipapo.c
> @@ -902,12 +902,14 @@ static void pipapo_lt_bits_adjust(struct nft_pipapo_field *f)
> static int pipapo_insert(struct nft_pipapo_field *f, const uint8_t *k,
> int mask_bits)
> {
> - int rule = f->rules++, group, ret, bit_offset = 0;
> + int rule = f->rules, group, ret, bit_offset = 0;
>
> - ret = pipapo_resize(f, f->rules - 1, f->rules);
> + ret = pipapo_resize(f, f->rules, f->rules + 1);
> if (ret)
> return ret;
>
> + f->rules++;
> +
> for (group = 0; group < f->groups; group++) {
> int i, v;
> u8 mask;
> @@ -1052,7 +1054,9 @@ static int pipapo_expand(struct nft_pipapo_field *f,
> step++;
> if (step >= len) {
> if (!masks) {
> - pipapo_insert(f, base, 0);
> + err = pipapo_insert(f, base, 0);
> + if (err < 0)
> + return err;
> masks = 1;
> }
> goto out;
> @@ -1235,6 +1239,9 @@ static int nft_pipapo_insert(const struct net *net, const struct nft_set *set,
> else
> ret = pipapo_expand(f, start, end, f->groups * f->bb);
>
> + if (ret < 0)
> + return ret;
> +
> if (f->bsize > bsize_max)
> bsize_max = f->bsize;
>
> --
> 2.41.0
>
prev parent reply other threads:[~2023-08-23 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 7:27 [PATCH nf] netfilter: nft_set_pipapo: fix out of memory error handling Florian Westphal
2023-08-23 9:06 ` Stefano Brivio
2023-08-23 9:10 ` Pablo Neira Ayuso [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=ZOXNHp3U5o1pSTno@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=sbrivio@redhat.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).