From: Christoph Hellwig <hch@infradead.org>
To: Jann Horn <jannh@google.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page-writeback: document folio_mark_dirty() locking more explicitly
Date: Mon, 10 Aug 2026 10:36:53 -0700 [thread overview]
Message-ID: <anoMNezqJ10YgcoN@infradead.org> (raw)
In-Reply-To: <20260810-set-page-dirty-warnings-v1-1-53cad4890808@google.com>
On Mon, Aug 10, 2026 at 06:02:36PM +0200, Jann Horn wrote:
> I have found two out-of-tree driver bugs in the past where set_page_dirty()
> was used on a page from GUP without appropriate locking, leading to UAF:
More documentation is always good, but out of tree drivers are totally
irrelevant for upstream, so please reword your commit message to be
relevant for the kernel itself and drop these references.
next prev parent reply other threads:[~2026-08-10 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 16:02 [PATCH] mm/page-writeback: document folio_mark_dirty() locking more explicitly Jann Horn
2026-08-10 17:36 ` Christoph Hellwig [this message]
2026-08-10 18:29 ` Jann Horn
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=anoMNezqJ10YgcoN@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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