All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzbot+bebc6f1acdf4cbb79b03@syzkaller.appspotmail.com,
	gnault@redhat.com, bcodding@redhat.com
Subject: Re: [PATCH net] inet: control sockets should not use current thread task_frag
Date: Thu, 05 Jan 2023 04:44:11 +0000	[thread overview]
Message-ID: <167289385150.19861.4532286036655661620.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230103192736.454149-1-edumazet@google.com>

Hello:

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

On Tue,  3 Jan 2023 19:27:36 +0000 you wrote:
> Because ICMP handlers run from softirq contexts,
> they must not use current thread task_frag.
> 
> Previously, all sockets allocated by inet_ctl_sock_create()
> would use the per-socket page fragment, with no chance of
> recursion.
> 
> [...]

Here is the summary with links:
  - [net] inet: control sockets should not use current thread task_frag
    https://git.kernel.org/netdev/net/c/1ac885574470

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



      parent reply	other threads:[~2023-01-05  4:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 19:27 [PATCH net] inet: control sockets should not use current thread task_frag Eric Dumazet
2023-01-03 22:38 ` Guillaume Nault
2023-01-05  4:44 ` 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=167289385150.19861.4532286036655661620.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bcodding@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=gnault@redhat.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+bebc6f1acdf4cbb79b03@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.