From: patchwork-bot+netdevbpf@kernel.org
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: davem@davemloft.net, johan@kernel.org, kuba@kernel.org,
oneukum@suse.com, mail@anirudhrb.com, zhengyongjun3@huawei.com,
geert@linux-m68k.org, kernel@esmil.dk, rkovhaev@gmail.com,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2 net] net: hso: check for allocation failure in hso_create_bulk_serial_device()
Date: Mon, 17 May 2021 21:00:09 +0000 [thread overview]
Message-ID: <162128520990.2358.2101615152759777465.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <YJ6IMH7jI9QFdGIX@mwanda>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 14 May 2021 17:24:48 +0300 you wrote:
> In current kernels, small allocations never actually fail so this
> patch shouldn't affect runtime.
>
> Originally this error handling code written with the idea that if
> the "serial->tiocmget" allocation failed, then we would continue
> operating instead of bailing out early. But in later years we added
> an unchecked dereference on the next line.
>
> [...]
Here is the summary with links:
- [v2,net] net: hso: check for allocation failure in hso_create_bulk_serial_device()
https://git.kernel.org/netdev/net/c/31db0dbd7244
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-05-17 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 10:09 [PATCH net] net: hso: check for allocation failure in hso_create_bulk_serial_device() Dan Carpenter
2021-05-12 10:19 ` Johan Hovold
2021-05-12 13:12 ` Dan Carpenter
2021-05-14 14:24 ` [PATCH v2 " Dan Carpenter
2021-05-17 8:07 ` Johan Hovold
2021-05-17 21: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=162128520990.2358.2101615152759777465.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=johan@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@esmil.dk \
--cc=kuba@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=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 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).