From: Jann Horn <jannh@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-MM <linux-mm@kvack.org>,
kernel list <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
John Hubbard <jhubbard@nvidia.com>, Jan Kara <jack@suse.cz>,
stable <stable@vger.kernel.org>, Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v2] mm/gup: fix try_grab_compound_head() race with split_huge_page()
Date: Tue, 15 Jun 2021 04:38:08 +0200 [thread overview]
Message-ID: <CAG48ez1uODg-_6LrLsLzCoBr=VEBisfeNhSkTmYgwG0Ldq+Dxg@mail.gmail.com> (raw)
In-Reply-To: <CAG48ez1nZcrJPO-hOLyE08g8HKSGEambCp6mNv6FNR2c9+6sJg@mail.gmail.com>
On Tue, Jun 15, 2021 at 4:36 AM Jann Horn <jannh@google.com> wrote:
> If you don't like the ifdeffery in this patch, can you please merge
> the v1 patch? It's not like I was adding a new BUG_ON(), I was just
> refactoring an existing BUG_ON() into a helper function, so I wasn't
> making things worse; and I don't want to think about how to best
> design WARN/BUG macros for the VM subsystem in order to land this
> bugfix.
Ah, nevermind, I hadn't seen that you already merged this one.
next prev parent reply other threads:[~2021-06-15 2:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 1:20 [PATCH v2] mm/gup: fix try_grab_compound_head() race with split_huge_page() Jann Horn
2021-06-15 2:00 ` Andrew Morton
2021-06-15 2:36 ` Jann Horn
2021-06-15 2:36 ` Jann Horn
2021-06-15 2:38 ` Jann Horn [this message]
2021-06-15 2:38 ` Jann Horn
2021-06-15 6:37 ` John Hubbard
2021-06-15 12:09 ` Jann Horn
2021-06-15 12:09 ` Jann Horn
2021-06-15 23:10 ` Yang Shi
2021-06-15 23:10 ` Yang Shi
2021-06-16 17:27 ` Vlastimil Babka
2021-06-16 18:40 ` Yang Shi
2021-06-16 18:40 ` Yang Shi
2021-06-17 16:09 ` Vlastimil Babka
2021-06-18 13:25 ` Jason Gunthorpe
2021-06-18 13:50 ` Matthew Wilcox
2021-06-18 14:58 ` Jason Gunthorpe
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='CAG48ez1uODg-_6LrLsLzCoBr=VEBisfeNhSkTmYgwG0Ldq+Dxg@mail.gmail.com' \
--to=jannh@google.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=stable@vger.kernel.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 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.