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: 
 <172808163225.2763206.12562210220343838241.git-patchwork-notify@kernel.org>
Date: Fri, 04 Oct 2024 22:40:32 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Kory Maincent <kory.maincent@...tlin.com>
Cc: andrew@...n.ch, kuba@...nel.org, netdev@...r.kernel.org,
 linux-kernel@...r.kernel.org, kyle.swenson@....tech,
 thomas.petazzoni@...tlin.com, o.rempel@...gutronix.de, davem@...emloft.net,
 edumazet@...gle.com, pabeni@...hat.com
Subject: Re: [PATCH net] net: pse-pd: Fix enabled status mismatch

Hello:

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

On Wed,  2 Oct 2024 14:17:05 +0200 you wrote:
> PSE controllers like the TPS23881 can forcefully turn off their
> configuration state. In such cases, the is_enabled() and get_status()
> callbacks will report the PSE as disabled, while admin_state_enabled
> will show it as enabled. This mismatch can lead the user to attempt
> to enable it, but no action is taken as admin_state_enabled remains set.
> 
> The solution is to disable the PSE before enabling it, ensuring the
> actual status matches admin_state_enabled.
> 
> [...]

Here is the summary with links:
  - [net] net: pse-pd: Fix enabled status mismatch
    https://git.kernel.org/netdev/net/c/dda3529d2e84

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