public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: bugzilla-daemon@kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [Bug 218226] New: XFS: Assertion failed: bp->b_flags & XBF_DONE, file: fs/xfs/xfs_trans_buf.c, line: 241
Date: Tue, 5 Dec 2023 16:41:55 +1100	[thread overview]
Message-ID: <ZW64I2Ol+5FCXJG+@dread.disaster.area> (raw)
In-Reply-To: <bug-218226-201763@https.bugzilla.kernel.org/>

On Tue, Dec 05, 2023 at 03:22:44AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=218226
> 
>             Bug ID: 218226
>            Summary: XFS: Assertion failed: bp->b_flags & XBF_DONE, file:
>                     fs/xfs/xfs_trans_buf.c, line: 241
>            Product: File System
>            Version: 2.5
>           Hardware: All
>                 OS: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P3
>          Component: XFS
>           Assignee: filesystem_xfs@kernel-bugs.kernel.org
>           Reporter: mcgrof@kernel.org
>         Regression: No
> 
> While doing fstests baseline testing on v6.6-rc5 with kdevops [0] we found that
> the XFS assertion with:
> 
> XFS: Assertion failed: bp->b_flags & XBF_DONE, file: fs/xfs/xfs_trans_buf.c,
> line: 241

Known issue.

https://lore.kernel.org/linux-xfs/20231128153808.GA19360@lst.de/

-Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2023-12-05  5:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05  3:22 [Bug 218226] New: XFS: Assertion failed: bp->b_flags & XBF_DONE, file: fs/xfs/xfs_trans_buf.c, line: 241 bugzilla-daemon
2023-12-05  3:40 ` [Bug 218226] " bugzilla-daemon
2023-12-05  3:50 ` bugzilla-daemon
2023-12-05  5:16 ` bugzilla-daemon
2023-12-05  5:41 ` Dave Chinner [this message]
2023-12-05  5:42 ` bugzilla-daemon

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=ZW64I2Ol+5FCXJG+@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=bugzilla-daemon@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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