From: David Sterba <dsterba@suse.cz>
To: dsterba@suse.cz, "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Christoph Hellwig <hch@infradead.org>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org,
"Gustavo A . R . Silva" <gustavoars@kernel.org>
Subject: Re: [PATCH] btrfs: add special case to setget helpers for 64k pages
Date: Wed, 28 Jul 2021 18:00:16 +0200 [thread overview]
Message-ID: <20210728160015.GP5047@twin.jikos.cz> (raw)
In-Reply-To: <20210728153242.GN5047@twin.jikos.cz>
On Wed, Jul 28, 2021 at 05:32:42PM +0200, David Sterba wrote:
> On Wed, Jul 14, 2021 at 06:37:01PM -0500, Gustavo A. R. Silva wrote:
> > Is it OK with you if we proceed to enable -Warray-bounds in linux-next,
> > in the meantime?
>
> Yes, I've checked the development queue and there are no warnings from
> fs/btrfs/.
Sorry, not yet, there's the other issue that happens on 64k pages that
lead to a 1 element extent_buffer::pages. I can emulate that and see the
warning
fs/btrfs/disk-io.c: In function ‘csum_tree_block’:
fs/btrfs/disk-io.c:226:34: warning: array subscript 1 is above array bounds of ‘struct page *[1]’ [-Warray-bounds]
226 | kaddr = page_address(buf->pages[i]);
| ~~~~~~~~~~^~~
./include/linux/mm.h:1630:48: note: in definition of macro ‘page_address’
1630 | #define page_address(page) lowmem_page_address(page)
| ^~~~
In file included from fs/btrfs/ctree.h:32,
from fs/btrfs/disk-io.c:23:
fs/btrfs/extent_io.h:98:15: note: while referencing ‘pages’
98 | struct page *pages[1];
| ^~~~~
but that's easy to fix with
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -210,7 +210,7 @@ void btrfs_set_buffer_lockdep_class(u64 objectid, struct extent_buffer *eb,
static void csum_tree_block(struct extent_buffer *buf, u8 *result)
{
struct btrfs_fs_info *fs_info = buf->fs_info;
- const int num_pages = fs_info->nodesize >> PAGE_SHIFT;
+ const int num_pages = num_extent_pages(buf);
const int first_page_part = min_t(u32, PAGE_SIZE, fs_info->nodesize);
SHASH_DESC_ON_STACK(shash, fs_info->csum_shash);
char *kaddr;
---
I'll send a patch, it'll appear in for-next soonish.
prev parent reply other threads:[~2021-07-28 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 16:00 [PATCH] btrfs: add special case to setget helpers for 64k pages David Sterba
2021-07-01 21:57 ` Gustavo A. R. Silva
2021-07-01 23:59 ` Qu Wenruo
2021-07-02 0:09 ` Gustavo A. R. Silva
2021-07-02 0:21 ` Qu Wenruo
2021-07-02 0:39 ` Gustavo A. R. Silva
2021-07-02 0:39 ` Qu Wenruo
2021-07-02 1:09 ` Gustavo A. R. Silva
2021-07-02 10:22 ` David Sterba
2021-07-02 7:10 ` Christoph Hellwig
2021-07-02 11:06 ` David Sterba
2021-07-05 8:33 ` Christoph Hellwig
2021-07-08 14:34 ` David Sterba
2021-07-14 23:37 ` Gustavo A. R. Silva
2021-07-28 15:32 ` David Sterba
2021-07-28 16:00 ` David Sterba [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=20210728160015.GP5047@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=hch@infradead.org \
--cc=linux-btrfs@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).