From: Matthew Wilcox <willy@infradead.org>
To: "Aithal, Srikanth" <sraithal@amd.com>
Cc: kernel test robot <oliver.sang@intel.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-next:master] [mm] bbcbf2a3f0: kernel_BUG_at_mm/memory.c
Date: Thu, 21 Dec 2023 04:30:59 +0000 [thread overview]
Message-ID: <ZYO/g/Dg0+DN59Gq@casper.infradead.org> (raw)
In-Reply-To: <2b7ae17e-0429-47ab-8101-00486ef9841e@amd.com>
On Thu, Dec 21, 2023 at 08:26:37AM +0530, Aithal, Srikanth wrote:
> Starting from next-20231214 until next-20231220 have noted regression where
> kernel hangs randomly while running virtualization tests [multiple
> start-shutdown and reboot] against AMD sev guest type, with below call
> trace:
This is an entirely different problem, already reported and fix sent
about 24 hours ago.
diff --git a/mm/swap_state.c b/mm/swap_state.c
index 793b5b9e4f96..8a3a8f1ab20a 100644
--- a/mm/swap_state.c
+++ b/mm/swap_state.c
@@ -894,6 +894,9 @@ struct page *swapin_readahead(swp_entry_t entry, gfp_t gfp_mask,
swap_vma_readahead(entry, gfp_mask, mpol, ilx, vmf) :
swap_cluster_readahead(entry, gfp_mask, mpol, ilx);
mpol_cond_put(mpol);
+
+ if (!folio)
+ return NULL;
return folio_file_page(folio, swp_offset(entry));
}
prev parent reply other threads:[~2023-12-21 4:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 15:46 kernel test robot
2023-12-20 22:11 ` Andrew Morton
2023-12-20 22:29 ` David Hildenbrand
2023-12-21 11:23 ` Oliver Sang
2023-12-21 11:32 ` David Hildenbrand
2023-12-21 21:58 ` Andrew Morton
2023-12-21 22:07 ` David Hildenbrand
2023-12-21 22:13 ` Matthew Wilcox
2023-12-21 22:14 ` David Hildenbrand
2023-12-22 8:13 ` Oliver Sang
2023-12-22 9:38 ` David Hildenbrand
2023-12-21 2:56 ` Aithal, Srikanth
2023-12-21 4:30 ` Matthew Wilcox [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=ZYO/g/Dg0+DN59Gq@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=sraithal@amd.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