Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2] net/qla3xxx: fix schedule while atomic in ql_sem_spinlock
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <162155100993.27401.529271178627433178.git-patchwork-notify@kernel.org>
Date:   Thu, 20 May 2021 22:50:09 +0000
References: <1621513956-23060-1-git-send-email-zheyuma97@gmail.com>
In-Reply-To: <1621513956-23060-1-git-send-email-zheyuma97@gmail.com>
To:     Zheyu Ma <zheyuma97@gmail.com>
Cc:     GR-Linux-NIC-Dev@marvell.com, davem@davemloft.net, kuba@kernel.org,
        netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Thu, 20 May 2021 12:32:36 +0000 you wrote:
> When calling the 'ql_sem_spinlock', the driver has already acquired the
> spin lock, so the driver should not call 'ssleep' in atomic context.
> 
> This bug can be fixed by using 'mdelay' instead of 'ssleep'.
> 
> The KASAN's log reveals it:
> 
> [...]

Here is the summary with links:
  - [v2] net/qla3xxx: fix schedule while atomic in ql_sem_spinlock
    https://git.kernel.org/netdev/net/c/13a6f3153922

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