public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Genes Lists <lists@sapience.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	snitzer@kernel.org, song@kernel.org, yukuai3@huawei.com,
	axboe@kernel.dk, mpatocka@redhat.com, heinzm@redhat.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux RAID <linux-raid@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>
Cc: Bhanu Victor DiCara <00bvd0+linux@gmail.com>,
	Xiao Ni <xni@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: md raid6 oops in 6.6.4 stable
Date: Thu, 7 Dec 2023 22:42:44 +0800	[thread overview]
Message-ID: <714b22c7-b8dd-008d-a1ea-a184dc8ec1cf@linux.dev> (raw)
In-Reply-To: <be56b5df-fef8-4dbe-bb98-f6370a692d6e@sapience.com>

Hi,

On 12/7/23 21:55, Genes Lists wrote:
> On 12/7/23 08:30, Bagas Sanjaya wrote:
>> On Thu, Dec 07, 2023 at 08:10:04AM -0500, Genes Lists wrote:
>>> I have not had chance to git bisect this but since it happened in 
>>> stable I
>>> thought it was important to share sooner than later.
>>>
>>> One possibly relevant commit between 6.6.3 and 6.6.4 could be:
>>>
>>>    commit 2c975b0b8b11f1ffb1ed538609e2c89d8abf800e
>>>    Author: Song Liu <song@kernel.org>
>>>    Date:   Fri Nov 17 15:56:30 2023 -0800
>>>
>>>      md: fix bi_status reporting in md_end_clone_io
>>>
>>> log attached shows page_fault_oops.
>>> Machine was up for 3 days before crash happened.

Could you decode the oops (I can't find it in lore for some reason) 
([1])? And
can it be reproduced reliably? If so, pls share the reproduce step.

[1]. https://lwn.net/Articles/592724/

Thanks,
Guoqing

  reply	other threads:[~2023-12-07 14:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 13:10 md raid6 oops in 6.6.4 stable Genes Lists
2023-12-07 13:30 ` Bagas Sanjaya
2023-12-07 13:55   ` Genes Lists
2023-12-07 14:42     ` Guoqing Jiang [this message]
2023-12-07 15:58       ` Genes Lists
2023-12-07 17:37         ` Song Liu
2023-12-07 19:27           ` Genes Lists
2023-12-07 13:58   ` Thorsten Leemhuis
2023-12-08  2:05     ` Bagas Sanjaya
2023-12-07 16:15 ` Xiao Ni

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=714b22c7-b8dd-008d-a1ea-a184dc8ec1cf@linux.dev \
    --to=guoqing.jiang@linux.dev \
    --cc=00bvd0+linux@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bagasdotme@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heinzm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@sapience.com \
    --cc=mpatocka@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=snitzer@kernel.org \
    --cc=song@kernel.org \
    --cc=xni@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox