public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Lin Ma <linma@zju.edu.cn>
Cc: krzk@kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, mudongliangabcd@gmail.com,
	syzbot+43475bf3cfbd6e41f5b7@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] nfc/nci: fix race with opening and closing
Date: Fri, 18 Nov 2022 12:40:16 +0000	[thread overview]
Message-ID: <166877521677.4012.14328581399116193880.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221116130249.10232-1-linma@zju.edu.cn>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed, 16 Nov 2022 21:02:49 +0800 you wrote:
> Previously we leverage NCI_UNREG and the lock inside nci_close_device to
> prevent the race condition between opening a device and closing a
> device. However, it still has problem because a failed opening command
> will erase the NCI_UNREG flag and allow another opening command to
> bypass the status checking.
> 
> This fix corrects that by making sure the NCI_UNREG is held.
> 
> [...]

Here is the summary with links:
  - [v2] nfc/nci: fix race with opening and closing
    https://git.kernel.org/netdev/net/c/0ad6bded175e

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



      reply	other threads:[~2022-11-18 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 13:02 [PATCH v2] nfc/nci: fix race with opening and closing Lin Ma
2022-11-18 12: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=166877521677.4012.14328581399116193880.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linma@zju.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mudongliangabcd@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+43475bf3cfbd6e41f5b7@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox