[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z7vz7gBrbtE4foSI@casper.infradead.org>
Date: Mon, 24 Feb 2025 04:22:06 +0000
From: Matthew Wilcox <willy@...radead.org>
To: mawupeng <mawupeng1@...wei.com>
Cc: 21cnbao@...il.com, akpm@...ux-foundation.org, david@...hat.com,
kasong@...cent.com, ryan.roberts@....com, chrisl@...nel.org,
huang.ying.caritas@...il.com, schatzberg.dan@...il.com,
hanchuanhua@...o.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: swap: Avoid infinite loop if no valid swap entry
found during do_swap_page
On Mon, Feb 24, 2025 at 09:27:38AM +0800, mawupeng wrote:
> On 2025/2/23 14:18, Barry Song wrote:
> > On Sun, Feb 23, 2025 at 3:42 PM Matthew Wilcox <willy@...radead.org> wrote:
> >> On Sat, Feb 22, 2025 at 11:59:53AM +0800, mawupeng wrote:
> >>> On 2025/2/22 11:45, Matthew Wilcox wrote:
> >>>> On Sat, Feb 22, 2025 at 10:46:17AM +0800, Wupeng Ma wrote:
> >>>>> Digging into the source, we found that the swap entry is invalid due to
> >>>>> unknown reason, and this lead to invalid swap_info_struct. Excessive log
> >>>>> printing can fill up the prioritized log space, leading to the purging of
> >>>>> originally valid logs and hindering problem troubleshooting. To make this
> >>>>> more robust, kill this task.
>
> Yes, log flooding is not the main issue here, endless #PF is rather a more serious
> problem.
Then don't write the report as if the log flooding is the real problem.
Powered by blists - more mailing lists