From: Rustam Kovhaev <rkovhaev@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
Fengfei Xi <xi.fengfei@h3c.com>,
darrick.wong@oracle.com, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org, tian.xianting@h3c.com
Subject: Re: [PATCH] xfs: fix system crash caused by null bp->b_pages
Date: Fri, 24 Sep 2021 19:16:42 -0700 [thread overview]
Message-ID: <YU6GioPsUlVXbtwQ@nuc10> (raw)
In-Reply-To: <20210922014804.GQ1756565@dread.disaster.area>
Hi Dave,
On Wed, Sep 22, 2021 at 11:48:04AM +1000, Dave Chinner wrote:
> On Tue, Sep 21, 2021 at 03:48:13PM -0700, Rustam Kovhaev wrote:
> > Hi Fengfei, Eric,
> >
> > On Thu, Dec 24, 2020 at 01:35:32PM -0600, Eric Sandeen wrote:
> > > On 12/24/20 3:51 AM, Fengfei Xi wrote:
> > > > We have encountered the following problems several times:
> > > > 1、A raid slot or hardware problem causes block device loss.
> > > > 2、Continue to issue IO requests to the problematic block device.
> > > > 3、The system possibly crash after a few hours.
> > >
> > > What kernel is this on?
> > >
> >
> > I have a customer that recently hit this issue on 4.12.14-122.74
> > SLE12-SP5 kernel.
>
> I think need to engage SuSE support and engineering, then, as this
> is not a kernel supported by upstream devs. I'd be saying the same
> thing if this was an RHEL frankenkernel, too.
>
roger that, should not be a problem, thank you!
next prev parent reply other threads:[~2021-09-25 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 9:51 [PATCH] xfs: fix system crash caused by null bp->b_pages Fengfei Xi
2020-12-24 19:35 ` Eric Sandeen
2021-09-21 22:48 ` Rustam Kovhaev
2021-09-22 1:48 ` Dave Chinner
2021-09-25 2:16 ` Rustam Kovhaev [this message]
2024-04-28 3:44 ` Fengfei Xi
2024-05-01 22:59 ` Darrick J. Wong
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=YU6GioPsUlVXbtwQ@nuc10 \
--to=rkovhaev@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=tian.xianting@h3c.com \
--cc=xi.fengfei@h3c.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.