Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 10 Aug 2022 17:09:37 +0100
From:   Matthew Wilcox <willy@infradead.org>
To:     Hugh Dickins <hughd@google.com>
Cc:     Zdenek Kabelac <zkabelac@redhat.com>,
        LKML <linux-kernel@vger.kernel.org>,
        intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk,
        Andrew Morton <akpm@linux-foundation.org>
Subject: Re: i915: crash with 5.19-rc2
Message-ID: <YvPYQeMjfyruTeGe@casper.infradead.org>
References: <584ae788-05e3-5824-8c85-cbb833677850@redhat.com>
 <f0dd80b2-97e1-c320-8517-7ebdb027f58a@redhat.com>
 <4a204620-7639-c844-455-10e55b372bcf@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4a204620-7639-c844-455-10e55b372bcf@google.com>
Precedence: bulk

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.

Andrew, I have two fixes that I don't see in your tree:

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.