From: Greg KH <gregkh@linuxfoundation.org>
To: Walt Holman <walt@holmansrus.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6.1 0000/1146] 6.1.2-rc1 review
Date: Thu, 29 Dec 2022 08:13:14 +0100 [thread overview]
Message-ID: <Y60+ClXkkBAfKhUf@kroah.com> (raw)
In-Reply-To: <933489772.83.1672266579857.JavaMail.zimbra@holmansrus.com>
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
next prev parent reply other threads:[~2022-12-29 7:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 22:29 [PATCH 6.1 0000/1146] 6.1.2-rc1 review Walt Holman
2022-12-29 7:13 ` Greg KH [this message]
2022-12-29 12:57 ` Walt Holman
2022-12-29 15:54 ` Walt Holman
2022-12-30 9:33 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-12-29 18:30 Ronald Warsow
2022-12-28 14:25 Greg Kroah-Hartman
2022-12-28 15:10 ` Guenter Roeck
2022-12-28 17:38 ` Sasha Levin
2022-12-28 17:46 ` Justin Forbes
2022-12-28 20:03 ` Florian Fainelli
2022-12-28 20:46 ` Slade Watkins
2022-12-28 21:15 ` Daniel Díaz
2022-12-28 21:31 ` Guenter Roeck
2022-12-29 12:46 ` Sasha Levin
2022-12-29 3:41 ` Ron Economos
2022-12-29 3:57 ` Wang Yugui
2022-12-29 7:09 ` Greg Kroah-Hartman
2022-12-29 14:14 ` Wang Yugui
2022-12-30 9:33 ` Greg Kroah-Hartman
2022-12-29 7:47 ` Thierry Reding
2022-12-29 12:46 ` Bagas Sanjaya
2022-12-29 13:44 ` Guenter Roeck
2022-12-29 16:21 ` Naresh Kamboju
2022-12-29 23:24 ` Shuah Khan
2022-12-30 5:35 ` Rudi Heitbaum
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=Y60+ClXkkBAfKhUf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=walt@holmansrus.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