From: Keith Busch <kbusch@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-block@vger.kernel.org
Subject: Re: [bug report] block: fix leaking page ref on truncated direct io
Date: Tue, 12 Jul 2022 12:56:38 -0600 [thread overview]
Message-ID: <Ys3D5jQuR2/u8zNC@kbusch-mbp> (raw)
In-Reply-To: <Ys02ZQ+ekH1b0Dtl@kili>
On Tue, Jul 12, 2022 at 11:52:53AM +0300, Dan Carpenter wrote:
> Hello Keith Busch,
>
> The patch 7b1ccdf617ca: "block: fix leaking page ref on truncated
> direct io" from Jul 5, 2022, leads to the following Smatch static
> checker warning:
>
> block/bio.c:1254 __bio_iov_iter_get_pages()
> error: uninitialized symbol 'i'.
Yeah, this one was not ready to be merged into any staging trees. One of the
build-bots even flagged this patch hours after it was initially posted.
I've a v2 posted with the appropriate correction, and I'll sort it out with the
maintainers on next steps.
prev parent reply other threads:[~2022-07-12 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 8:52 [bug report] block: fix leaking page ref on truncated direct io Dan Carpenter
2022-07-12 18:56 ` Keith Busch [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=Ys3D5jQuR2/u8zNC@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-block@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox