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,
	horms@kernel.org, idosch@nvidia.com, netdev@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net 0/2] drop_monitor: take care of 32bit kernels
Date: Thu, 23 Jul 2026 18:10:21 +0000	[thread overview]
Message-ID: <178483022188.2811828.635720735981502576.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260722141743.3266924-1-edumazet@google.com>

Hello:

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

On Wed, 22 Jul 2026 14:17:41 +0000 you wrote:
> This series fixes two drop_monitor issues on 32-bit architectures:
> 
> - Patch 1 uses nla_total_size_64bit() for PC and TIMESTAMP attributes to
>   account for alignment padding added by nla_put_u64_64bit(), avoiding
>   potential skb_over_panic() crashes.
> 
> - Patch 2 moves u64_stats updates before spin_unlock_irqrestore(), ensuring
>   local interrupts are disabled to prevent seqcount corruption from nested
>   interrupts in probe context.
> 
> [...]

Here is the summary with links:
  - [v2,net,1/2] drop_monitor: fix size calculations for 64-bit attributes
    https://git.kernel.org/netdev/net/c/7089f7ab99c8
  - [v2,net,2/2] drop_monitor: perform u64_stats updates under IRQ-disabled section
    https://git.kernel.org/netdev/net/c/fd098a23bf8f

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-07-23 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 14:17 [PATCH v2 net 0/2] drop_monitor: take care of 32bit kernels Eric Dumazet
2026-07-22 14:17 ` [PATCH v2 net 1/2] drop_monitor: fix size calculations for 64-bit attributes Eric Dumazet
2026-07-22 14:17 ` [PATCH v2 net 2/2] drop_monitor: perform u64_stats updates under IRQ-disabled section Eric Dumazet
2026-07-23 18: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=178483022188.2811828.635720735981502576.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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.