lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <163415760703.2895.9979622967812805701.git-patchwork-notify@kernel.org>
Date:   Wed, 13 Oct 2021 20:40:07 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Vladimir Oltean <vladimir.oltean@....com>
Cc:     netdev@...r.kernel.org, kuba@...nel.org, davem@...emloft.net,
        f.fainelli@...il.com, andrew@...n.ch, vivien.didelot@...il.com,
        olteanv@...il.com
Subject: Re: [PATCH net-next] net: dsa: unregister cross-chip notifier after
 ds->ops->teardown

Hello:

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

On Tue, 12 Oct 2021 15:37:35 +0300 you wrote:
> To be symmetric with the error unwind path of dsa_switch_setup(), call
> dsa_switch_unregister_notifier() after ds->ops->teardown.
> 
> The implication is that ds->ops->teardown cannot emit cross-chip
> notifiers. For example, currently the dsa_tag_8021q_unregister() call
> from sja1105_teardown() does not propagate to the entire tree due to
> this reason. However I cannot find an actual issue caused by this,
> observed using code inspection.
> 
> [...]

Here is the summary with links:
  - [net-next] net: dsa: unregister cross-chip notifier after ds->ops->teardown
    https://git.kernel.org/netdev/net-next/c/39e222bfd7f3

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ