From: Dan Carpenter <dan.carpenter@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jessica Clarke <jrtc27@jrtc27.com>,
kernel test robot <lkp@intel.com>,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-riscv@lists.infradead.org, linux-rdma@vger.kernel.org,
linux-pci@vger.kernel.org, linux-parport@lists.infradead.org,
linux-omap@vger.kernel.org, linux-mm@kvack.org,
linux-fbdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
dri-devel@lists.freedesktop.org, bpf@vger.kernel.org,
amd-gfx@lists.freedesktop.org, alsa-devel@alsa-project.org
Subject: Re: [linux-next:master] BUILD REGRESSION 8cb8311e95e3bb58bd84d6350365f14a718faa6d
Date: Thu, 26 May 2022 11:48:32 +0300 [thread overview]
Message-ID: <20220526084832.GC2146@kadam> (raw)
In-Reply-To: <Yo7U8kglHlcvQ0Ri@casper.infradead.org>
On Thu, May 26, 2022 at 02:16:34AM +0100, Matthew Wilcox wrote:
> Bizarre this started showing up now. The recent patch was:
>
> - info->alloced += compound_nr(page);
> - inode->i_blocks += BLOCKS_PER_PAGE << compound_order(page);
> + info->alloced += folio_nr_pages(folio);
> + inode->i_blocks += BLOCKS_PER_PAGE << folio_order(folio);
>
> so it could tell that compound_order() was small, but folio_order()
> might be large?
The old code also generates a warning on my test system. Smatch thinks
both compound_order() and folio_order() are 0-255. I guess because of
the "unsigned char compound_order;" in the struct page.
regards,
dan carpenter
next prev parent reply other threads:[~2022-05-26 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 21:35 [linux-next:master] BUILD REGRESSION 8cb8311e95e3bb58bd84d6350365f14a718faa6d kernel test robot
2022-05-25 21:50 ` Andrew Morton
2022-05-25 22:07 ` Jessica Clarke
2022-05-25 22:20 ` Andrew Morton
2022-05-26 1:16 ` Matthew Wilcox
2022-05-26 8:48 ` Dan Carpenter [this message]
2022-05-26 14:28 ` Matthew Wilcox
2022-05-26 15:03 ` Dan Carpenter
2022-05-26 8:19 ` Dan Carpenter
2022-05-26 8:32 ` Arnd Bergmann
2022-06-16 5:11 ` Chen, Rong A
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=20220526084832.GC2146@kadam \
--to=dan.carpenter@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bpf@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jrtc27@jrtc27.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=willy@infradead.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).