From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [bug report] buffer: hoist GFP flags from grow_dev_page() to __getblk_gfp()
Date: Wed, 27 Sep 2023 16:03:50 +0100 [thread overview]
Message-ID: <ZRREVnPX8cinFZZp@casper.infradead.org> (raw)
In-Reply-To: <ZRREEIwqiy5DijKB@casper.infradead.org>
... you know, it helps if one actually ccs akpm when one want him to do
something ...
On Wed, Sep 27, 2023 at 04:02:40PM +0100, Matthew Wilcox wrote:
> On Wed, Sep 27, 2023 at 10:40:21AM +0300, Dan Carpenter wrote:
> > Hello Matthew Wilcox (Oracle),
> >
> > The patch a3c38500d469: "buffer: hoist GFP flags from grow_dev_page()
> > to __getblk_gfp()" from Sep 14, 2023 (linux-next), leads to the
> > following Smatch static checker warning:
> >
> > fs/buffer.c:1065 grow_dev_page()
> > warn: NEW missing error code 'ret'
>
> Andrew, please add this -fix patch to "buffer: hoist GFP flags from
> grow_dev_page() to __getblk_gfp()". I'll send a further cleanup patch
> to make the return values a bit more meaningful.
>
> diff --git a/fs/buffer.c b/fs/buffer.c
> index 3fe293c9f3ca..b1610202eb5c 100644
> --- a/fs/buffer.c
> +++ b/fs/buffer.c
> @@ -1060,6 +1060,7 @@ grow_dev_page(struct block_device *bdev, sector_t block,
> goto failed;
> }
>
> + ret = -ENOMEM;
> bh = folio_alloc_buffers(folio, size, gfp | __GFP_ACCOUNT);
> if (!bh)
> goto failed;
prev parent reply other threads:[~2023-09-27 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 7:40 [bug report] buffer: hoist GFP flags from grow_dev_page() to __getblk_gfp() Dan Carpenter
2023-09-27 14:52 ` Matthew Wilcox
2023-09-27 15:02 ` Matthew Wilcox
2023-09-27 15:03 ` Matthew Wilcox [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=ZRREVnPX8cinFZZp@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).