mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: <yangtengteng@bytedance.com>
Cc: edumazet@google.com, kuniyu@amazon.com, pabeni@redhat.com,
	willemb@google.com, davem@davemloft.net, kuba@kernel.org,
	horms@kernel.org, wuyun.abel@bytedance.com,
	shakeel.butt@linux.dev, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, zhoufeng.zf@bytedance.com,
	wangdongdong.6@bytedance.com, zhangrui.rod@bytedance.com,
	yangzhenze@bytedance.com
Subject: Re: [PATCH net-next v2] Fix sock_exceed_buf_limit not being triggered in __sk_mem_raise_allocated
Date: Thu, 29 May 2025 04:10:33 +0000	[thread overview]
Message-ID: <174849183349.2759302.11005825928372039491.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250527030419.67693-1-yangtengteng@bytedance.com>

Hello:

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

On Tue, 27 May 2025 11:04:19 +0800 you wrote:
> From: Tengteng Yang <yangtengteng@bytedance.com>
> 
> When a process under memory pressure is not part of any cgroup and
> the charged flag is false, trace_sock_exceed_buf_limit was not called
> as expected.
> 
> This regression was introduced by commit 2def8ff3fdb6 ("sock:
> Code cleanup on __sk_mem_raise_allocated()"). The fix changes the
> default value of charged to true while preserving existing logic.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] Fix sock_exceed_buf_limit not being triggered in __sk_mem_raise_allocated
    https://git.kernel.org/netdev/net/c/8542d6fac25c

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



      reply	other threads:[~2025-05-29  4:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27  3:04 yangtengteng
2025-05-29  4:10 ` 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=174849183349.2759302.11005825928372039491.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shakeel.butt@linux.dev \
    --cc=wangdongdong.6@bytedance.com \
    --cc=willemb@google.com \
    --cc=wuyun.abel@bytedance.com \
    --cc=yangtengteng@bytedance.com \
    --cc=yangzhenze@bytedance.com \
    --cc=zhangrui.rod@bytedance.com \
    --cc=zhoufeng.zf@bytedance.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
all inboxes | Powered by JetHome®