public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e0e774741360f6c74414@syzkaller.appspotmail.com>
To: allison.henderson@oracle.com, amir73il@gmail.com, cem@kernel.org,
	 darrick.wong@oracle.com, dchinner@redhat.com, hch@lst.de,
	 hsiangkao@redhat.com, linux-kernel@vger.kernel.org,
	linux-xfs@vger.kernel.org,  syzkaller-bugs@googlegroups.com
Subject: [syzbot] [xfs?] WARNING: Reset corrupted AGFL on AG NUM. NUM blocks leaked. Please unmount and run xfs_repair. (2)
Date: Tue, 08 Apr 2025 05:49:25 -0700	[thread overview]
Message-ID: <67f51b55.050a0220.107db6.05a9.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    e48e99b6edf4 Merge tag 'pull-fixes' of git://git.kernel.or..
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12b18be4580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=695196aa2bd08d99
dashboard link: https://syzkaller.appspot.com/bug?extid=e0e774741360f6c74414
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11aea7cf980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1727c94c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bacf2069a3a3/disk-e48e99b6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6b2b20d05f13/vmlinux-e48e99b6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a5ab8f6aba17/bzImage-e48e99b6.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/635c0241b9a9/mount_0.gz
  fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1327c94c580000)

The issue was bisected to:

commit 29887a22713192509cfc6068ea3b200cdb8856da
Author: Darrick J. Wong <darrick.wong@oracle.com>
Date:   Mon Aug 17 17:00:01 2020 +0000

    xfs: enable big timestamps

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16ceafb0580000
final oops:     https://syzkaller.appspot.com/x/report.txt?x=15ceafb0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=11ceafb0580000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e0e774741360f6c74414@syzkaller.appspotmail.com
Fixes: 29887a227131 ("xfs: enable big timestamps")

XFS (loop0): Mounting V5 Filesystem d7dc424e-7990-42cb-9f91-9cb7200a101d
XFS (loop0): Ending clean mount
XFS (loop0): WARNING: Reset corrupted AGFL on AG 0. 1 blocks leaked. Please unmount and run xfs_repair.
XFS (loop0): Unmounting Filesystem d7dc424e-7990-42cb-9f91-9cb7200a101d


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

                 reply	other threads:[~2025-04-08 12:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=67f51b55.050a0220.107db6.05a9.GAE@google.com \
    --to=syzbot+e0e774741360f6c74414@syzkaller.appspotmail.com \
    --cc=allison.henderson@oracle.com \
    --cc=amir73il@gmail.com \
    --cc=cem@kernel.org \
    --cc=darrick.wong@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=hch@lst.de \
    --cc=hsiangkao@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.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