From: Miklos Szeredi <miklos@szeredi.hu>
To: Antonio SJ Musumeci <trapexit@spawn.link>
Cc: fuse-devel <fuse-devel@lists.sourceforge.net>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [fuse-devel] trying to steal weird page?
Date: Thu, 20 Apr 2017 15:29:20 +0200 [thread overview]
Message-ID: <20170420132920.GA5214@veci.piliscsaba.szeredi.hu> (raw)
In-Reply-To: <CAB3-ZyT5pPc68BiQ2aC4r1608YgaN5U4H8TjddPN9jiUTE0rRg@mail.gmail.com>
On Wed, Apr 12, 2017 at 11:30:00AM -0400, Antonio SJ Musumeci wrote:
> A user reported getting the below errors when *not* using direct_io
> but atomic_o_trunc, auto_cache, big_writes, default_permissions,
> splice_move, splice_read, and splice_write are enabled.
>
> Any ideas?
I think this is due to the PageWaiters bit added in v4.10 by
62906027091f ("mm: add PageWaiters indicating tasks are waiting for a page bit")
That bit is harmless and probably left behind due to a race. Following patch
should fix the warning.
Thanks,
Miklos
---
fs/fuse/dev.c | 1 +
1 file changed, 1 insertion(+)
--- a/fs/fuse/dev.c
+++ b/fs/fuse/dev.c
@@ -811,6 +811,7 @@ static int fuse_check_page(struct page *
1 << PG_uptodate |
1 << PG_lru |
1 << PG_active |
+ 1 << PG_waiters |
1 << PG_reclaim))) {
printk(KERN_WARNING "fuse: trying to steal weird page\n");
printk(KERN_WARNING " page=%p index=%li flags=%08lx, count=%i, mapcount=%i, mapping=%p\n", page, page->index, page->flags, page_count(page), page_mapcount(page), page->mapping);
parent reply other threads:[~2017-04-20 13:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAB3-ZyT5pPc68BiQ2aC4r1608YgaN5U4H8TjddPN9jiUTE0rRg@mail.gmail.com>]
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=20170420132920.GA5214@veci.piliscsaba.szeredi.hu \
--to=miklos@szeredi.hu \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=trapexit@spawn.link \
/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).