From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: stable@vger.kernel.org, bpf@vger.kernel.org,
"Sasha Levin" <sashal@kernel.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Pu Lehui" <pulehui@huawei.com>
Subject: Re: [PATCH 5.10 v2 0/3] Re-adapt "bpf: Fix DEVMAP_HASH overflow check on 32-bit arches"
Date: Tue, 1 Oct 2024 10:09:13 +0200 [thread overview]
Message-ID: <2024100108-limit-decree-c642@gregkh> (raw)
In-Reply-To: <20240927135118.1432057-1-pulehui@huaweicloud.com>
On Fri, Sep 27, 2024 at 01:51:15PM +0000, Pu Lehui wrote:
> Commit 70294d8bc31f ("bpf: Eliminate rlimit-based memory accounting for
> devmap maps") relies on the v5.11+ basic mechanism of memcg-based memory
> accounting [0]. The commit cannot be independently backported to the
> 5.10 stable branch, otherwise the related memory when creating devmap
> will be unrestricted and the associated bpf selftest map_ptr will fail.
> Let's roll back to rlimit-based memory accounting mode for devmap and
> re-adapt the commit 225da02acdc9 ("bpf: Fix DEVMAP_HASH overflow check
> on 32-bit arches") to the 5.10 stable branch.
>
> Link: https://lore.kernel.org/bpf/20201201215900.3569844-1-guro@fb.com [0]
>
> Pu Lehui (2):
> Revert "bpf: Fix DEVMAP_HASH overflow check on 32-bit arches"
> Revert "bpf: Eliminate rlimit-based memory accounting for devmap maps"
>
> Toke Høiland-Jørgensen (1):
> bpf: Fix DEVMAP_HASH overflow check on 32-bit arches
>
> kernel/bpf/devmap.c | 20 ++++++++++++++++++--
> 1 file changed, 18 insertions(+), 2 deletions(-)
>
> --
> 2.34.1
>
>
Now queud up, thanks.
greg k-h
prev parent reply other threads:[~2024-10-01 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 13:51 [PATCH 5.10 v2 0/3] Re-adapt "bpf: Fix DEVMAP_HASH overflow check on 32-bit arches" Pu Lehui
2024-09-27 13:51 ` [PATCH 5.10 v2 1/3] Revert " Pu Lehui
2024-09-27 13:51 ` [PATCH 5.10 v2 2/3] Revert "bpf: Eliminate rlimit-based memory accounting for devmap maps" Pu Lehui
2024-09-27 13:51 ` [PATCH 5.10 v2 3/3] bpf: Fix DEVMAP_HASH overflow check on 32-bit arches Pu Lehui
2024-10-01 8:09 ` 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=2024100108-limit-decree-c642@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bpf@vger.kernel.org \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=toke@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.