public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Hugh Dickins <hughd@google.com>,
	Zdenek Kabelac <zkabelac@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: i915: crash with 5.19-rc2
Date: Wed, 10 Aug 2022 14:54:31 -0700	[thread overview]
Message-ID: <20220810145431.71d9bfda20decb357cc208ec@linux-foundation.org> (raw)
In-Reply-To: <YvPYQeMjfyruTeGe@casper.infradead.org>

On Wed, 10 Aug 2022 17:09:37 +0100 Matthew Wilcox <willy@infradead.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.


      reply	other threads:[~2022-08-10 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 11:18 i915: crash with 5.19-rc2 Zdenek Kabelac
2022-06-22 20:46 ` [Intel-gfx] " Rodrigo Vivi
2022-06-23  9:32   ` Zdenek Kabelac
2022-08-10  9:22 ` Zdenek Kabelac
2022-08-10 15:55   ` Hugh Dickins
2022-08-10 16:09     ` Matthew Wilcox
2022-08-10 21:54       ` Andrew Morton [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=20220810145431.71d9bfda20decb357cc208ec@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=hughd@google.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@infradead.org \
    --cc=zkabelac@redhat.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