From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
Zack Rusin <zackr@vmware.com>,
Hans de Goede <hdegoede@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: regression: NULL pointer dereference due to 27599aacbaef ("fbdev: Hot-unplug firmware fb devices on forced removal")
Date: Tue, 5 Apr 2022 14:06:03 +0100 [thread overview]
Message-ID: <CADVatmMdBmU9E4XEnc8Y=JdvUKVvVgawJWtHqojW5hFHkkfaJQ@mail.gmail.com> (raw)
In-Reply-To: <1116eb70-516e-13b3-0697-4af00430bae8@suse.de>
On Mon, Apr 4, 2022 at 8:46 PM Thomas Zimmermann <tzimmermann@suse.de> wrote:
>
> Hi
>
> Am 31.03.22 um 10:25 schrieb Sudip Mukherjee:
> > On Thu, Mar 31, 2022 at 8:07 AM Thomas Zimmermann <tzimmermann@suse.de> wrote:
> >>
> >>
> >>
> >> Am 28.03.22 um 17:41 schrieb Sudip Mukherjee:
> >>> Hi Thomas,
> >>>
> >>> We usually run boot tests with linux mainline HEAD commit almost every
> >>> night on ppc64 qemu. And my tests had been failing for last few days.
> >>
> >> Could you please provide your kernel's config file?
> >
> > Thanks for taking a look at it.
> > The config is attached.
> >
> >
>
> I was able to reproduce and fix the issue locally. Please have a look at
> [1] for the patch.
Thanks Thomas.
And I can confirm it fixes the problem for me too.
Tested-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
--
Regards
Sudip
prev parent reply other threads:[~2022-04-05 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 15:41 regression: NULL pointer dereference due to 27599aacbaef ("fbdev: Hot-unplug firmware fb devices on forced removal") Sudip Mukherjee
2022-03-30 12:36 ` Thorsten Leemhuis
2022-03-31 7:02 ` Thomas Zimmermann
2022-03-31 7:07 ` Thomas Zimmermann
2022-03-31 8:25 ` Sudip Mukherjee
2022-04-04 19:46 ` Thomas Zimmermann
2022-04-05 13:06 ` Sudip Mukherjee [this message]
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='CADVatmMdBmU9E4XEnc8Y=JdvUKVvVgawJWtHqojW5hFHkkfaJQ@mail.gmail.com' \
--to=sudipm.mukherjee@gmail.com \
--cc=hdegoede@redhat.com \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.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;
as well as URLs for NNTP newsgroup(s).