All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, akpm@linux-foundation.org,
	dvyukov@google.com, kuni1840@gmail.com, netdev@vger.kernel.org,
	syzbot+f95c2f0a71a98cef50eb@syzkaller.appspotmail.com
Subject: Re: [PATCH v1 net] ref_tracker: Don't use __GFP_NOFAIL for PF_MEMALLOC thread.
Date: Fri, 02 Oct 2026 01:50:04 +0000	[thread overview]
Message-ID: <179090580478.3175897.3150668516679948132.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930220137.843785-1-kuniyu@google.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 30 Sep 2026 22:01:34 +0000 you wrote:
> syzbot triggered a warning in __alloc_pages_slowpath(). [0]
> 
> ref_tracker_alloc() uses __GFP_NOFAIL if the passed gfp has
> __GFP_DIRECT_RECLAIM.
> 
> However, cifs_demultiplex_thread() calls memalloc_noreclaim_save()
> and its kthread has PF_MEMALLOC.
> 
> [...]

Here is the summary with links:
  - [v1,net] ref_tracker: Don't use __GFP_NOFAIL for PF_MEMALLOC thread.
    https://git.kernel.org/netdev/net-next/c/071876fd5048

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



      parent reply	other threads:[~2026-10-02  1:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 22:01 [PATCH v1 net] ref_tracker: Don't use __GFP_NOFAIL for PF_MEMALLOC thread Kuniyuki Iwashima
2026-10-01  6:51 ` Eric Dumazet
2026-10-02  1:50 ` patchwork-bot+netdevbpf [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=179090580478.3175897.3150668516679948132.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+f95c2f0a71a98cef50eb@syzkaller.appspotmail.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.