linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [fuse-devel] trying to steal weird page?
       [not found] <CAB3-ZyT5pPc68BiQ2aC4r1608YgaN5U4H8TjddPN9jiUTE0rRg@mail.gmail.com>
@ 2017-04-20 13:29 ` Miklos Szeredi
  0 siblings, 0 replies; only message in thread
From: Miklos Szeredi @ 2017-04-20 13:29 UTC (permalink / raw)
  To: Antonio SJ Musumeci; +Cc: fuse-devel, linux-mm, linux-fsdevel, linux-kernel

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);

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2017-04-20 13:32 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAB3-ZyT5pPc68BiQ2aC4r1608YgaN5U4H8TjddPN9jiUTE0rRg@mail.gmail.com>
2017-04-20 13:29 ` [fuse-devel] trying to steal weird page? Miklos Szeredi

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).