From: patchwork-bot+netdevbpf@kernel.org
To: Anirudh Rayabharam <mail@anirudhrb.com>
Cc: davem@davemloft.net, kuba@kernel.org, oneukum@suse.com,
gregkh@linuxfoundation.org, geert@linux-m68k.org,
zhengyongjun3@huawei.com, rkovhaev@gmail.com, kernel@esmil.dk,
jgarzik@redhat.com, alan@lxorguk.ukuu.org.uk,
syzbot+c49fe6089f295a05e6f8@syzkaller.appspotmail.com,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: hso: fix null-ptr-deref during tty device unregistration
Date: Wed, 07 Apr 2021 22:20:28 +0000 [thread overview]
Message-ID: <161783402883.11274.17007849600420610230.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210407172726.29706-1-mail@anirudhrb.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 7 Apr 2021 22:57:22 +0530 you wrote:
> Multiple ttys try to claim the same the minor number causing a double
> unregistration of the same device. The first unregistration succeeds
> but the next one results in a null-ptr-deref.
>
> The get_free_serial_index() function returns an available minor number
> but doesn't assign it immediately. The assignment is done by the caller
> later. But before this assignment, calls to get_free_serial_index()
> would return the same minor number.
>
> [...]
Here is the summary with links:
- [v2] net: hso: fix null-ptr-deref during tty device unregistration
https://git.kernel.org/netdev/net/c/8a12f8836145
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:[~2021-04-07 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 17:27 [PATCH v2] net: hso: fix null-ptr-deref during tty device unregistration Anirudh Rayabharam
2021-04-07 22:20 ` 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=161783402883.11274.17007849600420610230.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jgarzik@redhat.com \
--cc=kernel@esmil.dk \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mail@anirudhrb.com \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=rkovhaev@gmail.com \
--cc=syzbot+c49fe6089f295a05e6f8@syzkaller.appspotmail.com \
--cc=zhengyongjun3@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.