BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@kernel.org, vbabka@suse.cz, linux-mm@kvack.org,
	kernel-team@fb.com
Subject: Re: [PATCH bpf-next] mm: Fix the flipped condition in gfpflags_allow_spinning()
Date: Mon, 10 Mar 2025 22:30:32 +0000	[thread overview]
Message-ID: <174164583201.3719472.12293725364552859716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250310124017.187-1-alexei.starovoitov@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Mon, 10 Mar 2025 13:40:17 +0100 you wrote:
> From: Vlastimil Babka <vbabka@suse.cz>
> 
> The function gfpflags_allow_spinning() has a bug that makes it return
> the opposite result than intended. This could contribute to deadlocks as
> usage profilerates, for now it was noticed as a performance regression
> due to try_charge_memcg() not refilling memcg stock when it could. Fix
> the flipped condition.
> 
> [...]

Here is the summary with links:
  - [bpf-next] mm: Fix the flipped condition in gfpflags_allow_spinning()
    https://git.kernel.org/bpf/bpf-next/c/157a50236c30

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2025-03-10 22:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10 12:40 [PATCH bpf-next] mm: Fix the flipped condition in gfpflags_allow_spinning() Alexei Starovoitov
2025-03-10 22:30 ` patchwork-bot+netdevbpf [this message]
     [not found] <202503101254.cfd454df-lkp@intel.com>
     [not found] ` <7c41d8d7-7d5a-4c3d-97b3-23642e376ff9@suse.cz>
     [not found]   ` <CAADnVQ+NKZtNxS+jBW=tMnmca18S2jfuGCR+ap1bPHYyhxy6HQ@mail.gmail.com>
     [not found]     ` <a30e2c60-e01b-4eac-8a40-e7a73abebfd3@suse.cz>
     [not found]       ` <CAADnVQ+g=VN6cOVzhF2ory0isXEc52W8fKx4KdwpYfOMvk372A@mail.gmail.com>
     [not found]         ` <9d8f5f92-5f4b-4732-af48-3ecaa41af81a@suse.cz>
2025-03-10 11:15           ` Fwd: [linux-next:master] [memcg] 01d37228d3: netperf.Throughput_Mbps 37.9% regression Alexei Starovoitov
2025-03-10 12:16             ` [PATCH bpf-next] mm: Fix the flipped condition in gfpflags_allow_spinning() Alexei Starovoitov
2025-03-10 16:03               ` Shakeel Butt

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=174164583201.3719472.12293725364552859716.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=linux-mm@kvack.org \
    --cc=martin.lau@kernel.org \
    --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