From: Shakeel Butt <shakeel.butt@linux.dev>
To: syzbot ci <syzbot+ciacf14517a343602e@syzkaller.appspotmail.com>
Cc: boris@bur.io, kernel-team@fb.com, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
willy@infradead.org, wqu@suse.com, syzbot@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot ci] Re: introduce uncharged file mapped folios
Date: Mon, 18 Aug 2025 09:36:53 -0700 [thread overview]
Message-ID: <d63fvoc3ans2d4xsuzsavchg3g6b3a5ao6osckrkwgwe3354zq@fp5nxj23krys> (raw)
In-Reply-To: <68a19424.050a0220.e29e5.0065.GAE@google.com>
On Sun, Aug 17, 2025 at 01:34:44AM -0700, syzbot ci wrote:
> syzbot ci has tested the following series
>
> [v2] introduce uncharged file mapped folios
> https://lore.kernel.org/all/cover.1755300815.git.boris@bur.io
> * [PATCH v2 1/3] mm/filemap: add AS_UNCHARGED
> * [PATCH v2 2/3] mm: add vmstat for cgroup uncharged pages
> * [PATCH v2 3/3] btrfs: set AS_UNCHARGED on the btree_inode
>
> and found the following issue:
> WARNING in folio_lruvec_lock_irqsave
Ok that is expected and we need to fix the warning instead. We can
either remove this warning or make is only applicable to non-file
folios.
prev parent reply other threads:[~2025-08-18 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 23:40 [PATCH v2 0/3] " Boris Burkov
2025-08-15 23:40 ` [PATCH v2 1/3] mm/filemap: add AS_UNCHARGED Boris Burkov
2025-08-16 0:41 ` Shakeel Butt
2025-08-15 23:40 ` [PATCH v2 2/3] mm: add vmstat for cgroup uncharged pages Boris Burkov
2025-08-16 0:48 ` Shakeel Butt
2025-08-16 0:54 ` Shakeel Butt
2025-08-15 23:40 ` [PATCH v2 3/3] btrfs: set AS_UNCHARGED on the btree_inode Boris Burkov
2025-08-16 0:50 ` Shakeel Butt
2025-08-16 12:52 ` David Sterba
2025-08-17 8:34 ` [syzbot ci] Re: introduce uncharged file mapped folios syzbot ci
2025-08-18 16:36 ` Shakeel Butt [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=d63fvoc3ans2d4xsuzsavchg3g6b3a5ao6osckrkwgwe3354zq@fp5nxj23krys \
--to=shakeel.butt@linux.dev \
--cc=boris@bur.io \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+ciacf14517a343602e@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
--cc=wqu@suse.com \
/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