From: Andrew Morton <akpm@linux-foundation.org>
To: Ivan Orlov <ivan.orlov0322@gmail.com>
Cc: Yang Shi <shy828301@gmail.com>,
linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org,
syzbot+9578faa5475acb35fa50@syzkaller.appspotmail.com,
Mike Kravetz <mike.kravetz@oracle.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
Zach O'Keefe <zokeefe@google.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH v2] mm: khugepaged: Fix kernel BUG in hpage_collapse_scan_file
Date: Tue, 18 Apr 2023 14:28:43 -0700 [thread overview]
Message-ID: <20230418142843.4ef62be30f529458344fa0e0@linux-foundation.org> (raw)
In-Reply-To: <5dc97e10-8c64-4818-2642-dd8edb21c016@gmail.com>
On Mon, 17 Apr 2023 22:28:51 +0400 Ivan Orlov <ivan.orlov0322@gmail.com> wrote:
> Tested today on the latest rc7, the bug still exists.
OK, thanks. I'll send this patch upstream during the next merge window.
If you, Zach or someone else decides to remove SCAN_STORE_FAILED and
perhaps those WARN_ON_ONCE()es then we can address these things later.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2023-04-18 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 15:53 [PATCH v2] mm: khugepaged: Fix kernel BUG in hpage_collapse_scan_file Ivan Orlov
2023-03-31 1:33 ` Zach O'Keefe via Linux-kernel-mentees
2023-03-31 6:47 ` Ivan Orlov
2023-04-04 0:58 ` Yang Shi
2023-04-05 16:43 ` Zach O'Keefe via Linux-kernel-mentees
2023-04-16 18:33 ` Andrew Morton
2023-04-16 20:39 ` Ivan Orlov
2023-04-16 23:04 ` Ivan Orlov
2023-04-17 0:45 ` Hugh Dickins via Linux-kernel-mentees
2023-04-17 18:28 ` Ivan Orlov
2023-04-18 21:28 ` 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=20230418142843.4ef62be30f529458344fa0e0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ivan.orlov0322@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=shy828301@gmail.com \
--cc=syzbot+9578faa5475acb35fa50@syzkaller.appspotmail.com \
--cc=willy@infradead.org \
--cc=zokeefe@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox