[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wi9XK=TQ7tk6+2ymx8Upm6r36vY6wF9REpt1sho2ySteg@mail.gmail.com>
Date: Mon, 22 Jan 2024 17:25:57 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@....com>
Cc: Steven Rostedt <rostedt@...dmis.org>, LKML <linux-kernel@...r.kernel.org>,
Felix Kuehling <Felix.Kuehling@....com>, Christian König <christian.koenig@....com>,
dri-devel@...ts.freedesktop.org
Subject: Re: [BUG] BUG: kernel NULL pointer dereference at ttm_device_init+0xb4
On Mon, 22 Jan 2024 at 16:56, Bhardwaj, Rajneesh
<rajneesh.bhardwaj@....com> wrote:
>
> I think a fix might already be in flight. Please see Linux-Kernel Archive: Re: [PATCH] drm/ttm: fix ttm pool initialization for no-dma-device drivers (iu.edu)
Please use lore.kernel.org that doesn't corrupt whitespace in patches
or lose header information:
https://lore.kernel.org/lkml/20240113213347.9562-1-pchelkin@ispras.ru/
although that seems to be a strange definition of "in flight". It was
sent out 8 days ago, and apparently nobody thought to include it in
the drm fixes pile that came in last Friday.
So it made it into rc1, even though it was reported a week before.
It also looks like some mailing list there is mangling emails - if you
use 'all' instead of 'lkml', lore reports multiple emails with the
same message-id, and it all looks messier as a result.
I assume it's dri-devel@...ts.freedesktop.org that messes up, mainly
because I don't tend to see this behaviour when only the usual
kernel.org mailing lists are involved.
Linus
Powered by blists - more mailing lists