From: Eryu Guan <eguan@redhat.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS: Assertion failed: bp->b_flags & XBF_ASYNC, file: fs/xfs/xfs_buf.c, line: 118 on 4.8-rc1 kernel
Date: Sat, 13 Aug 2016 14:50:56 +0800 [thread overview]
Message-ID: <20160813065056.GX27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160812170714.GA64450@bfoster.bfoster>
On Fri, Aug 12, 2016 at 01:07:15PM -0400, Brian Foster wrote:
> On Fri, Aug 12, 2016 at 10:47:52PM +0800, Eryu Guan wrote:
> > On Fri, Aug 12, 2016 at 10:04:14PM +0800, Eryu Guan wrote:
> > > Hi,
> > >
> > > I hit oops while building kernel on XFS, 4.8-rc1 kernel, hit twice in
> > > six kernel builds. I'm not sure if it's a regression since 4.7 kernel
> > > yet, will do more testings.
> >
> > Just hit again on 4.8-rc1 kernel, I was doing
> >
> > # clean partial builds from previous run and build again
> > make clean
> > make -j 8
> >
> > Seems I have to do kernel build on 4.7 kernel to finish the bisect.
> >
> > Thanks,
> > Eryu
> >
> > [ 2515.752039] XFS: Assertion failed: bp->b_flags & XBF_ASYNC, file: fs/xfs/xfs_buf.c, line: 118
>
> This is commit 9c7504aa7 ("xfs: track and serialize in-flight async
> buffers against unmount"). The assert is actually incorrect, as Dave had
> previously pointed out[1]. A patch was posted[2] to fix it, but hasn't
> been merged yet.
>
> Brian
>
> [1] http://oss.sgi.com/pipermail/xfs/2016-August/050613.html
> [2] http://oss.sgi.com/pipermail/xfs/2016-August/050634.html
Thanks for the reminder, I had impression of this thread and patch, but
didn't realize I was hitting the same problem. I don't have to do bisect
then :)
Thanks,
Eryu
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-08-13 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 14:04 XFS: Assertion failed: bp->b_flags & XBF_ASYNC, file: fs/xfs/xfs_buf.c, line: 118 on 4.8-rc1 kernel Eryu Guan
2016-08-12 14:47 ` Eryu Guan
2016-08-12 17:07 ` Brian Foster
2016-08-13 6:50 ` Eryu Guan [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=20160813065056.GX27776@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=bfoster@redhat.com \
--cc=xfs@oss.sgi.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