linux-kernel - Re: [PATCH 6.1 0000/1146] 6.1.2-rc1 review

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]

Message-ID: <Y60+ClXkkBAfKhUf@kroah.com>
Date:   Thu, 29 Dec 2022 08:13:14 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Walt Holman <walt@...mansrus.com>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 6.1 0000/1146] 6.1.2-rc1 review

On Wed, Dec 28, 2022 at 04:29:39PM -0600, Walt Holman wrote:
> > This is the start of the stable review cycle for the 6.1.2 release.
> > There are 1146 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Fri, 30 Dec 2022 14:41:29 +0000.
> > Anything received after that time might be too late.
> > 
> > The whole patch series can be found in one patch at:
> > [ https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.2-rc1.gz | https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.2-rc1.gz ] > or in the git tree and branch at:
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> > and the diffstat can be found below.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > ------------- 
> 
> Hello, 
> 
> I'm getting a NULL Pointer Dereference when shutting down or rebooting. It happens just as it tries to shut down the swap device ( /dev/dm-3 ). This happens late in the shutdown process and nothing gets saved in the logs. However, I've attached a photo of my screen showing the Oops and stack trace. Let me know if there's anything you'd like me to try. 

Does this happen with 6.1.1 also?

Can you use 'git bisect' to track down the offending change?

thanks,

greg k-h