From: Ming Lei <ming.lei@redhat.com>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
yukuai3@huawei.com, linux-next <linux-next@vger.kernel.org>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [next-20220225][Oops][ppc] lvm snapshot merge results kernel panics (throtl_pending_timer_fn)
Date: Wed, 2 Mar 2022 16:25:45 +0800 [thread overview]
Message-ID: <Yh8qCS5JM8ZbtqY4@T590> (raw)
In-Reply-To: <d583adf0-2d98-60b6-620c-722912c05852@linux.vnet.ibm.com>
On Wed, Mar 02, 2022 at 01:31:39PM +0530, Abdul Haleem wrote:
> Greeting's
>
> Linux next kernel 5.17.0-rc5-next-20220225 crashed on my power 10 LPAR when
> merge lvm snapshot on nvme disk
Please try next-20220301, in which the "bad" patch of 'block: cancel all
throttled bios in del_gendisk()' is dropped.
Thanks,
Ming
WARNING: multiple messages have this Message-ID (diff)
From: Ming Lei <ming.lei@redhat.com>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: axboe@kernel.dk, linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org,
linux-next <linux-next@vger.kernel.org>,
yukuai3@huawei.com, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [next-20220225][Oops][ppc] lvm snapshot merge results kernel panics (throtl_pending_timer_fn)
Date: Wed, 2 Mar 2022 16:25:45 +0800 [thread overview]
Message-ID: <Yh8qCS5JM8ZbtqY4@T590> (raw)
In-Reply-To: <d583adf0-2d98-60b6-620c-722912c05852@linux.vnet.ibm.com>
On Wed, Mar 02, 2022 at 01:31:39PM +0530, Abdul Haleem wrote:
> Greeting's
>
> Linux next kernel 5.17.0-rc5-next-20220225 crashed on my power 10 LPAR when
> merge lvm snapshot on nvme disk
Please try next-20220301, in which the "bad" patch of 'block: cancel all
throttled bios in del_gendisk()' is dropped.
Thanks,
Ming
next prev parent reply other threads:[~2022-03-02 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 8:01 [next-20220225][Oops][ppc] lvm snapshot merge results kernel panics (throtl_pending_timer_fn) Abdul Haleem
2022-03-02 8:01 ` Abdul Haleem
2022-03-02 8:25 ` Ming Lei [this message]
2022-03-02 8:25 ` Ming Lei
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=Yh8qCS5JM8ZbtqY4@T590 \
--to=ming.lei@redhat.com \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=yukuai3@huawei.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 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.