From: Michal Hocko <mhocko@suse.com>
To: Florian Westphal <fw@strlen.de>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, vbabka@suse.cz,
akpm@linux-foundation.org, urezki@gmail.com,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
Martin Zaharinov <micron10@gmail.com>
Subject: Re: [PATCH mm] mm: fix BUG with kvzalloc+GFP_ATOMIC
Date: Mon, 26 Sep 2022 11:30:06 +0200 [thread overview]
Message-ID: <YzFxHlYoncuDl2fM@dhcp22.suse.cz> (raw)
In-Reply-To: <YzFplwSxwwsLpzzX@dhcp22.suse.cz>
On Mon 26-09-22 10:58:00, Michal Hocko wrote:
[...]
> A better option to me seems to be reworking the rhashtable_insert_rehash
> to not rely on an atomic allocation. I am not familiar with that code
> but it seems to me that the only reason this allocation mode is used is
> due to rcu locking around rhashtable_try_insert. Is there any reason we
> cannot drop the rcu lock, allocate with the full GFP_KERNEL allocation
> power and retry with the pre allocated object? rhashtable_insert_slow is
> already doing that to implement its never fail semantic.
So a very blunt and likely not 100% correct take on this side of things.
But it should give an idea at least.
---
diff --git a/lib/rhashtable.c b/lib/rhashtable.c
index e12bbfb240b8..fc547c43b05d 100644
--- a/lib/rhashtable.c
+++ b/lib/rhashtable.c
@@ -437,31 +437,11 @@ static void rht_deferred_worker(struct work_struct *work)
}
static int rhashtable_insert_rehash(struct rhashtable *ht,
- struct bucket_table *tbl)
+ struct bucket_table *tbl,
+ struct bucket_table *new_tbl)
{
- struct bucket_table *old_tbl;
- struct bucket_table *new_tbl;
- unsigned int size;
int err;
- old_tbl = rht_dereference_rcu(ht->tbl, ht);
-
- size = tbl->size;
-
- err = -EBUSY;
-
- if (rht_grow_above_75(ht, tbl))
- size *= 2;
- /* Do not schedule more than one rehash */
- else if (old_tbl != tbl)
- goto fail;
-
- err = -ENOMEM;
-
- new_tbl = bucket_table_alloc(ht, size, GFP_ATOMIC | __GFP_NOWARN);
- if (new_tbl == NULL)
- goto fail;
-
err = rhashtable_rehash_attach(ht, tbl, new_tbl);
if (err) {
bucket_table_free(new_tbl);
@@ -471,17 +451,6 @@ static int rhashtable_insert_rehash(struct rhashtable *ht,
schedule_work(&ht->run_work);
return err;
-
-fail:
- /* Do not fail the insert if someone else did a rehash. */
- if (likely(rcu_access_pointer(tbl->future_tbl)))
- return 0;
-
- /* Schedule async rehash to retry allocation in process context. */
- if (err == -ENOMEM)
- schedule_work(&ht->run_work);
-
- return err;
}
static void *rhashtable_lookup_one(struct rhashtable *ht,
@@ -619,9 +588,33 @@ static void *rhashtable_try_insert(struct rhashtable *ht, const void *key,
}
} while (!IS_ERR_OR_NULL(new_tbl));
- if (PTR_ERR(data) == -EAGAIN)
- data = ERR_PTR(rhashtable_insert_rehash(ht, tbl) ?:
+ if (PTR_ERR(data) == -EAGAIN) {
+ struct bucket_table *old_tbl;
+ unsigned int size;
+
+ old_tbl = rht_dereference_rcu(ht->tbl, ht);
+ size = tbl->size;
+
+ data = ERR_PTR(-EBUSY);
+
+ if (rht_grow_above_75(ht, tbl))
+ size *= 2;
+ /* Do not schedule more than one rehash */
+ else if (old_tbl != tbl)
+ return data;
+
+ data = ERR_PTR(-ENOMEM);
+
+ rcu_read_unlock();
+ new_tbl = bucket_table_alloc(ht, size, GFP_KERNEL);
+ rcu_read_lock();
+
+ if (!new_tbl)
+ return data;
+
+ data = ERR_PTR(rhashtable_insert_rehash(ht, tbl, new_tbl) ?:
-EAGAIN);
+ }
return data;
}
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2022-09-26 9:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 10:38 Florian Westphal
2022-09-23 13:29 ` Michal Hocko
2022-09-23 13:35 ` Florian Westphal
2022-09-23 14:43 ` Uladzislau Rezki
2022-09-23 14:54 ` Florian Westphal
2022-09-23 15:10 ` Uladzislau Rezki
2022-09-26 15:03 ` Vlastimil Babka
2022-09-26 15:28 ` Sebastian Andrzej Siewior
2022-09-26 7:49 ` Michal Hocko
2022-09-26 7:56 ` Florian Westphal
2022-09-26 8:57 ` Michal Hocko
2022-09-26 9:30 ` Michal Hocko [this message]
2022-09-26 10:08 ` Florian Westphal
2022-09-26 12:02 ` Michal Hocko
2022-09-26 13:08 ` Florian Westphal
2022-09-26 13:38 ` Florian Westphal
2022-09-26 14:05 ` Michal Hocko
2022-09-26 14:20 ` Florian Westphal
2022-09-26 14:32 ` Michal Hocko
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=YzFxHlYoncuDl2fM@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=micron10@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
/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