linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Rustam Kovhaev <rkovhaev@gmail.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: Wed, 22 Sep 2021 11:48:04 +1000	[thread overview]
Message-ID: <20210922014804.GQ1756565@dread.disaster.area> (raw)
In-Reply-To: <YUphLS+pXoVwPxMz@nuc10>

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.

> Here is my backtrace:
> [965887.179651] XFS (veeamimage0): Mounting V5 Filesystem
> [965887.848169] XFS (veeamimage0): Starting recovery (logdev: internal)
> [965888.268088] XFS (veeamimage0): Ending recovery (logdev: internal)
> [965888.289466] XFS (veeamimage1): Mounting V5 Filesystem
> [965888.406585] XFS (veeamimage1): Starting recovery (logdev: internal)
> [965888.473768] XFS (veeamimage1): Ending recovery (logdev: internal)
> [986032.367648] XFS (veeamimage0): metadata I/O error: block 0x1044a20 ("xfs_buf_iodone_callback_error") error 5 numblks 32

Storage layers returned -EIO a second before things went bad.
Whether that is relevant cannot be determined from the information
provided.

> [986033.152809] BUG: unable to handle kernel NULL pointer dereference at           (null)
> [986033.152973] IP: xfs_buf_offset+0x2c/0x60 [xfs]
> [986033.153013] PGD 0 P4D 0 
> [986033.153041] Oops: 0000 [#1] SMP PTI
> [986033.153083] CPU: 13 PID: 48029 Comm: xfsaild/veeamim Tainted: P           OE      4.12.14-122.74-default #1 SLE12-SP5

And there are unknown proprietary modules loaded, so we can't trust
the code in the kernel to be operating correctly...

I'm not sure there's really anything upstream developers can help
with without any idea of how to reproduce this problem on a current
kernel...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2021-09-22  1:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  9:51 Fengfei Xi
2020-12-24 19:35 ` Eric Sandeen
2021-09-21 22:48   ` Rustam Kovhaev
2021-09-22  1:48     ` Dave Chinner [this message]
2021-09-25  2:16       ` Rustam Kovhaev

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=20210922014804.GQ1756565@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=rkovhaev@gmail.com \
    --cc=sandeen@sandeen.net \
    --cc=tian.xianting@h3c.com \
    --cc=xi.fengfei@h3c.com \
    --subject='Re: [PATCH] xfs: fix system crash caused by null bp->b_pages' \
    /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

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).