From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-mm@kvack.org, linux-xfs@vger.kernel.org, hch@lst.de,
osalvador@suse.de, elver@google.com, vbabka@suse.cz,
andreyknvl@gmail.com
Subject: Re: [PATCH 0/3] mm: fix nested allocation context filtering
Date: Thu, 2 May 2024 10:05:14 -0700 [thread overview]
Message-ID: <20240502100514.cce09f1fab6914a56491debf@linux-foundation.org> (raw)
In-Reply-To: <20240430054604.4169568-1-david@fromorbit.com>
On Tue, 30 Apr 2024 15:28:22 +1000 Dave Chinner <david@fromorbit.com> wrote:
> This patchset is the followup to the comment I made earlier today:
>
> https://lore.kernel.org/linux-xfs/ZjAyIWUzDipofHFJ@dread.disaster.area/
>
> Tl;dr: Memory allocations that are done inside the public memory
> allocation API need to obey the reclaim recursion constraints placed
> on the allocation by the original caller, including the "don't track
> recursion for this allocation" case defined by __GFP_NOLOCKDEP.
I resolved a number of conflicts here, mainly due to the addition
of GFP_NOLOCKDEP in stackdepot and page-owner.
https://lore.kernel.org/all/20240418141133.22950-1-ryabinin.a.a@gmail.com/T/#u
https://lkml.kernel.org/r/20240429082828.1615986-1-hch@lst.de
Please check the resulting code?
prev parent reply other threads:[~2024-05-02 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 5:28 [PATCH 0/3] mm: fix nested allocation context filtering Dave Chinner
2024-04-30 5:28 ` [PATCH 1/3] mm: lift gfp_kmemleak_mask() to gfp.h Dave Chinner
2024-04-30 12:39 ` Marco Elver
2024-04-30 5:28 ` [PATCH 2/3] stackdepot: use gfp_nested_mask() instead of open coded masking Dave Chinner
2024-04-30 12:39 ` Marco Elver
2024-04-30 5:28 ` [PATCH 3/3] mm/page-owner: " Dave Chinner
2024-04-30 9:35 ` [PATCH 0/3] mm: fix nested allocation context filtering Christoph Hellwig
2024-04-30 10:06 ` Vlastimil Babka
2024-05-01 8:06 ` Oscar Salvador
2024-05-02 17:05 ` Andrew Morton [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=20240502100514.cce09f1fab6914a56491debf@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=david@fromorbit.com \
--cc=elver@google.com \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=osalvador@suse.de \
--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 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.