From: Oscar Salvador <osalvador@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@linux-foundation.org, elver@google.com, vbabka@suse.cz,
andreyknvl@gmail.com, linux-mm@kvack.org, djwong@kernel.org,
david@fromorbit.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] mm,page_owner: don't remove __GFP_NOLOCKDEP in add_stack_record_to_list
Date: Mon, 29 Apr 2024 11:33:39 +0200 [thread overview]
Message-ID: <Zi9pc0RoVWCJ2aVn@localhost.localdomain> (raw)
In-Reply-To: <20240429082828.1615986-1-hch@lst.de>
On Mon, Apr 29, 2024 at 10:28:28AM +0200, Christoph Hellwig wrote:
> Otherwise we'll generate false lockdep positives.
>
> Fixes: 217b2119b9e2 ("mm,page_owner: implement the tracking of the stacks count")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Oscar Salvador <osalvador@suse.de>
--
Oscar Salvador
SUSE Labs
prev parent reply other threads:[~2024-04-29 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 8:28 [PATCH v2] mm,page_owner: don't remove __GFP_NOLOCKDEP in add_stack_record_to_list Christoph Hellwig
2024-04-29 8:32 ` Vlastimil Babka
2024-04-29 9:33 ` Oscar Salvador [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=Zi9pc0RoVWCJ2aVn@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=elver@google.com \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=vbabka@suse.cz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).