From: Kalle Valo <kvalo@codeaurora.org>
To: Alex Dewar <alex.dewar90@gmail.com>
Cc: unlisted-recipients:; (no To-header on input) Alex Dewar
<alex.dewar90@gmail.com>, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ath11k: Correctly check errors for calls to debugfs_create_dir()
Date: Thu, 1 Oct 2020 19:30:27 +0000 (UTC) [thread overview]
Message-ID: <20201001193027.0F73EC433CB@smtp.codeaurora.org> (raw)
In-Reply-To: <20200927132451.585473-1-alex.dewar90@gmail.com>
Alex Dewar <alex.dewar90@gmail.com> wrote:
> debugfs_create_dir() returns an ERR_PTR in case of error, but never a
> null pointer. There are a number of places where error-checking code can
> accordingly be simplified.
>
> Addresses-Coverity: CID 1497150: Memory - illegal accesses (USE_AFTER_FREE)
> Addresses-Coverity: CID 1497158: Memory - illegal accesses (USE_AFTER_FREE)
> Addresses-Coverity: CID 1497160: Memory - illegal accesses (USE_AFTER_FREE)
> Signed-off-by: Alex Dewar <alex.dewar90@gmail.com>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
476c1d3c2e61 ath11k: Correctly check errors for calls to debugfs_create_dir()
--
https://patchwork.kernel.org/patch/11802131/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-10-01 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 13:24 [PATCH] ath11k: Correctly check errors for calls to debugfs_create_dir() Alex Dewar
2020-10-01 19:30 ` Kalle Valo [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=20201001193027.0F73EC433CB@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=alex.dewar90@gmail.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).