All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Johan Hovold <johan@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	mail@anirudhrb.com, leoanto@aruba.it
Subject: Re: [PATCH] net: hso: fix NULL-deref on disconnect regression
Date: Mon, 26 Apr 2021 20:00:10 +0000	[thread overview]
Message-ID: <161946721024.23958.2611872115325420575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210426081149.10498-1-johan@kernel.org>

Hello:

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

On Mon, 26 Apr 2021 10:11:49 +0200 you wrote:
> Commit 8a12f8836145 ("net: hso: fix null-ptr-deref during tty device
> unregistration") fixed the racy minor allocation reported by syzbot, but
> introduced an unconditional NULL-pointer dereference on every disconnect
> instead.
> 
> Specifically, the serial device table must no longer be accessed after
> the minor has been released by hso_serial_tty_unregister().
> 
> [...]

Here is the summary with links:
  - net: hso: fix NULL-deref on disconnect regression
    https://git.kernel.org/netdev/net-next/c/2ad5692db728

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



      parent reply	other threads:[~2021-04-26 20:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26  8:11 [PATCH] net: hso: fix NULL-deref on disconnect regression Johan Hovold
2021-04-26  9:29 ` Leonardo Antoniazzi
2021-04-26  9:35   ` Johan Hovold
2021-04-26  9:50     ` Greg Kroah-Hartman
2021-04-26 20:09       ` David Miller
2021-04-27  6:11         ` Greg KH
2021-04-26 14:01 ` Anirudh Rayabharam
2021-04-26 20:00 ` 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=161946721024.23958.2611872115325420575.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leoanto@aruba.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mail@anirudhrb.com \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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.