From: patchwork-bot+netdevbpf@kernel.org
To: Manuel Ullmann <labre@posteo.de>
Cc: irusskikh@marvell.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, regressions@lists.linux.dev,
davem@davemloft.net, ndanilov@marvell.com, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com,
jordanleppert@protonmail.com, holger@applied-asynchrony.com,
kolman.jindrich@gmail.com
Subject: Re: [PATCH v6] net: atlantic: always deep reset on pm op, fixing up my null deref regression
Date: Tue, 10 May 2022 08:40:12 +0000 [thread overview]
Message-ID: <165217201275.28090.9247936511102323749.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <87bkw8dfmp.fsf@posteo.de>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 08 May 2022 00:36:46 +0000 you wrote:
> >From 18dc080d8d4a30d0fcb45f24fd15279cc87c47d5 Mon Sep 17 00:00:00 2001
> Date: Wed, 4 May 2022 21:30:44 +0200
>
> The impact of this regression is the same for resume that I saw on
> thaw: the kernel hangs and nothing except SysRq rebooting can be done.
>
> Fixes regression in commit cbe6c3a8f8f4 ("net: atlantic: invert deep
> par in pm functions, preventing null derefs"), where I disabled deep
> pm resets in suspend and resume, trying to make sense of the
> atl_resume_common() deep parameter in the first place.
>
> [...]
Here is the summary with links:
- [v6] net: atlantic: always deep reset on pm op, fixing up my null deref regression
https://git.kernel.org/netdev/net/c/1809c30b6e5a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-05-10 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 0:36 [PATCH v6] net: atlantic: always deep reset on pm op, fixing up my null deref regression Manuel Ullmann
2022-05-10 8:37 ` Paolo Abeni
2022-05-10 19:17 ` Manuel Ullmann
2022-05-10 8:40 ` 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=165217201275.28090.9247936511102323749.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=holger@applied-asynchrony.com \
--cc=irusskikh@marvell.com \
--cc=jordanleppert@protonmail.com \
--cc=kolman.jindrich@gmail.com \
--cc=kuba@kernel.org \
--cc=labre@posteo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ndanilov@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).