linux-kernel - Re: [git pull] drm for 6.10-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 15 May 2024 17:05:43 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dave Airlie <airlied@...il.com>
Cc: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@....com>, 
	Christian König <christian.koenig@....com>, 
	Matthew Auld <matthew.auld@...el.com>, Daniel Vetter <daniel.vetter@...ll.ch>, 
	dri-devel <dri-devel@...ts.freedesktop.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm for 6.10-rc1

On Wed, 15 May 2024 at 16:51, Dave Airlie <airlied@...il.com> wrote:
>
> > Let's see if the machine ends up being stable now. It took several
> > hours for the "scary messages" state to turn into the "hung machine"
> > state, so they *could* have been independent issues, but it seems a
> > bit unlikely.
>
> This worries me actually, it's possible this warn could cause a
> problem, but I'm not convinced it should have machine ending
> properties without some sort of different error at the end, so I'd
> keep an eye open here.

Well, since I'm a big believer in dogfooding, I always run my own
kernel even during the merge window. I don't reboot between each pull,
but I try to basically reboot daily.

And it's entirely possible that the eventual "bad page flags" error -
which is what I think triggered the eventual hang - is something else
that came in during this merge window.

I haven't actually gotten the -mm changes from Andrew yet, but it did
happen in the btrfs kworker, and I have merged the btrfs changes for
6.10.  So maybe they are the cause.

I was blaming the DRM case mainly because it clearly *was* about some
kind of allocation management, and I got a *lot* of those warnings:

    $ journalctl -b -1 | grep 'WARNING: CPU' | wc -1
      16015

but let's see if it happens with my amdgpu reverts in place, and no
drm warnings.

It most definitely wouldn't be the first time we had multiple
independent bugs during the merge window ;/

              Linus