[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d961070e-d261-4227-b044-dc73f9f8ca16@redhat.com>
Date: Thu, 20 Jun 2024 21:31:16 +0200
From: David Hildenbrand <david@...hat.com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, stable@...r.kernel.org,
patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com, srw@...dewatkins.net,
rwarsow@....de, conor@...nel.org, allen.lkml@...il.com, broonie@...nel.org,
Miaohe Lin <linmiaohe@...wei.com>, Arnd Bergmann <arnd@...db.de>,
Dan Carpenter <dan.carpenter@...aro.org>, Cgroups <cgroups@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, Baolin Wang <baolin.wang@...ux.alibaba.com>,
jbeulich@...e.com, LTP List <ltp@...ts.linux.it>
Subject: Re: [PATCH 6.9 000/281] 6.9.6-rc1 review
>>>>
>> Trying to connect the dots here, can you enlighten me how this is
>> related to the fork13 mainline report?
>
> I am not sure about the relation between these two reports.
> But as a common practice I have shared that report information.
Yes, I was just briefly concerned that we are seeing the same issue as
we saw once on 6.10-rc3 also on a 6.9 kernel -- also because the patch
list don't contain that much MM stuff.
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists