From: Christoph Hellwig <hch@infradead.org>
To: Ayush Jain <ayush.jain3@amd.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Karny, Wyes" <Wyes.Karny@amd.com>, Jens Axboe <axboe@kernel.dk>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"V, Narasimhan" <Narasimhan.V@amd.com>,
"Shetty, Kalpana" <Kalpana.Shetty@amd.com>,
"Shukla, Santosh" <Santosh.Shukla@amd.com>
Subject: Re: Kernel null pointer dereference on stopping raid device
Date: Wed, 14 Jun 2023 23:03:46 -0700 [thread overview]
Message-ID: <ZIqpwhu4Tfa9MDzM@infradead.org> (raw)
In-Reply-To: <fc7b82a6-a74a-7675-7cfd-4dd9ac10543b@amd.com>
On Thu, Jun 15, 2023 at 11:14:02AM +0530, Ayush Jain wrote:
> > That was just a quick hack to verify the problem. I think this is
> > the proper fix, can you try it as well?
> >
>
> Sure, this works on my machine.
>
> Tested-by: Ayush Jain <ayush.jain3@amd.com>
So it turns out that Jens merged the md pull request for 6.5 yesterday,
and that includes and equivalent change in
3ce94ce5d05ae89190a23f6187f64d8f4b2d3782
Author: Yu Kuai <yukuai3@huawei.com>
Date: Tue May 23 09:27:27 2023 +0800
md: fix duplicate filename for rdev
With that I think we don't need an extra fix. Sorry for all the
extra work.
prev parent reply other threads:[~2023-06-15 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 20:12 Kernel null pointer dereference on stopping raid device Jain, Ayush
2023-06-14 7:10 ` Ayush Jain
2023-06-14 7:22 ` Christoph Hellwig
[not found] ` <IA1PR12MB61375A452083D65B5FB815DBBA5AA@IA1PR12MB6137.namprd12.prod.outlook.com>
2023-06-14 14:01 ` Christoph Hellwig
2023-06-15 5:44 ` Ayush Jain
2023-06-15 6:03 ` Christoph Hellwig [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=ZIqpwhu4Tfa9MDzM@infradead.org \
--to=hch@infradead.org \
--cc=Kalpana.Shetty@amd.com \
--cc=Narasimhan.V@amd.com \
--cc=Santosh.Shukla@amd.com \
--cc=Wyes.Karny@amd.com \
--cc=axboe@kernel.dk \
--cc=ayush.jain3@amd.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.