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:   Thu, 29 Dec 2022 06:57:28 -0600 (CST)
From:   Walt Holman <walt@holmansrus.com>
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     linux-kernel <linux-kernel@vger.kernel.org>
Message-ID: <255732713.91.1672318648501.JavaMail.zimbra@holmansrus.com>
In-Reply-To: <Y60+ClXkkBAfKhUf@kroah.com>
References: <933489772.83.1672266579857.JavaMail.zimbra@holmansrus.com> <Y60+ClXkkBAfKhUf@kroah.com>
Subject: Re: [PATCH 6.1 0000/1146] 6.1.2-rc1 review
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: 6.1.2-rc1 review
Thread-Index: ersqxz6lVnikKAcGC4xoUSRYuHBNOQ==
Precedence: bulk

----- On Dec 29, 2022, at 1:13 AM, Greg KH gregkh@linuxfoundation.org wrote:

> 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

This does NOT happen with 6.1.1 I'll get on bisecting here in a bit. I'm wondering about the changes that were made to blk-mq.c  That's where the new quiesce code and the null pointer dereference occur. I'll start by rolling back that commit and see what happens before bisecting. 

-Walt