[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20220810145431.71d9bfda20decb357cc208ec@linux-foundation.org>
Date: Wed, 10 Aug 2022 14:54:31 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Hugh Dickins <hughd@...gle.com>,
Zdenek Kabelac <zkabelac@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
intel-gfx@...ts.freedesktop.org, chris@...is-wilson.co.uk
Subject: Re: i915: crash with 5.19-rc2
On Wed, 10 Aug 2022 17:09:37 +0100 Matthew Wilcox <willy@...radead.org> wrote:
> On Wed, Aug 10, 2022 at 08:55:32AM -0700, Hugh Dickins wrote:
> > This is not a bug in zram or i915, but what Matthew fixes in
> > https://lore.kernel.org/lkml/20220730042518.1264767-1-willy@infradead.org/
>
> Thanks for tracking that down, Hugh. Nice to know it's a crash rather
> than a data corruption. The fix is in Andrew's tree, so I think it's
> already destined for upstream soon.
Yes, that's in the hotfixes queue for sending upstream Fridayish.
> Andrew, I have two fixes that I don't see in your tree:
Is it expected to be in my tree? It's a huge v1 patch series on which
I wasn't cc'ed?
> https://lore.kernel.org/linux-mm/20220808193430.3378317-2-willy@infradead.org/T/#u
> https://lore.kernel.org/linux-mm/20220808193430.3378317-4-willy@infradead.org/T/#u
>
> The first is of minor importance, the second I believe Hugh has hit in
> his testing.
In that case the second patch should be pulled out of that series, have
its changelog made to describe the runtime effects and have a Cc:stable
added, please.
Powered by blists - more mailing lists