From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Yi Wen <shicenci@gmail.com>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
Jan Kara <jack@suse.cz>, John Hubbard <jhubbard@nvidia.com>,
Pedro Falcato <pfalcato@suse.de>
Subject: Re: [BUG] mm/gup: WARNING: mm/page-writeback.c:2678 at __folio_mark_dirty on v7.4-rc3
Date: Sat, 21 Nov 2026 17:44:34 +0100 [thread overview]
Message-ID: <f8cc1652-7577-4ace-97ed-081ecd65a031@kernel.org> (raw)
In-Reply-To: <CAPHJ_V+_=Av8pAM+N+oc4JRmtqBjhcimh3B_pSy_N+5qecm6Mg@mail.gmail.com>
On 11/21/26 15:49, Yi Wen wrote:
> Hi,
>
> I am reporting a kernel WARNING triggered by a syzkaller reproducer on
> Linux v7.4-rc3.
>
> The reproducer triggers a WARNING in ext4_dirty_folio() when
> process_vm_writev() writes to a file-backed mapping.
>
> The call trace shows that the warning occurs during the GUP page
> unpinning and dirtying path:
>
> process_vm_writev()
> -> process_vm_rw_core()
> -> unpin_user_pages_dirty_lock()
> -> folio_mark_dirty()
> -> ext4_dirty_folio()
>
> A second WARNING is subsequently triggered in __folio_mark_dirty() in
> mm/page-writeback.c.
>
> This appears to be related to the interaction between GUP-based page
> dirtying and filesystem-managed folio metadata. In particular, the GUP
> dirtying path may mark a file-backed folio dirty without ensuring that
> the filesystem-specific metadata required by its dirty_folio()
> implementation remains available.
>
> This may be related to the known issue where GUP-based page dirtying
> does not properly notify the filesystem through page_mkwrite(), as
> well as the interaction between GUP dirtying and
> filemap_release_folio().
>
> Before these warnings, all four ext4 loop devices also report delayed
> block allocation errors and abnormal free block accounting. These
> errors may indicate an additional filesystem inconsistency and are
> included in the console log for further investigation.
>
Hi,
thanks for the report.
Did you only find this through syzcaller or by the help of an LLM?
I'm asking because the timing is interesting; this should be one of the problems
discussed by:
https://lore.kernel.org/r/20261119-gup-dirty-what-v1-0-236d69f25c24@suse.de
CCing Pedro, John und Jan.
--
Cheers,
David
prev parent reply other threads:[~2026-11-21 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 14:49 [BUG] mm/gup: WARNING: mm/page-writeback.c:2678 at __folio_mark_dirty on v7.4-rc3 Yi Wen
2026-11-21 16:44 ` David Hildenbrand (Arm) [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=f8cc1652-7577-4ace-97ed-081ecd65a031@kernel.org \
--to=david@kernel.org \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pfalcato@suse.de \
--cc=shicenci@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.