From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandanrlinux@gmail.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: [PRBOMB] xfs: online repair patches for 6.9
Date: Fri, 23 Feb 2024 17:02:20 -0800 [thread overview]
Message-ID: <20240224010220.GN6226@frogsfrogsfrogs> (raw)
Hi Chandan,
Please pull these multiple pull requests containing all the online
repair functionality that Christoph and I managed to get reviewed in
time for 6.9.
--D
PS: Has anyone out there observed the following crash on arm64?
run fstests xfs/570 at 2024-02-22 20:32:17
spectre-v4 mitigation disabled by command-line option
XFS (sda2): Mounting V5 Filesystem 2fd78ebc-692d-46e1-bd8a-9f1591c007f6
XFS (sda2): Ending clean mount
XFS (sda2): EXPERIMENTAL online scrub feature in use. Use at your own risk!
XFS (sda3): Mounting V5 Filesystem ac0b0a07-294f-418e-b4d0-c14cc345fcd4
XFS (sda3): Ending clean mount
XFS (sda3): EXPERIMENTAL online scrub feature in use. Use at your own risk!
Unable to handle kernel paging request at virtual address ffffffff80206388
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006, ISS2 = 0x00000000
CM = 0, WnR = 0, TnD = 0, TagAccess = 0
GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
swapper pgtable: 64k pages, 42-bit VAs, pgdp=0000000040d40000
[ffffffff80206388] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000, pmd=0000000000000000
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Dumping ftrace buffer:
(ftrace buffer empty)
Modules linked in: xfs rpcsec_gss_krb5 auth_rpcgss nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defra
sch_fq_codel fuse configfs efivarfs ip_tables x_tables overlay nfsv4
CPU: 0 PID: 38 Comm: 0:1H Not tainted 6.8.0-rc4-djwa #rc4 892edfc98307d2cdb226d4164dfd6775c2b3b52c
Hardware name: QEMU KVM Virtual Machine, BIOS 1.6.6 08/22/2023
Workqueue: xfs-log/sda3 xlog_ioend_work [xfs]
pstate: a0401005 (NzCv daif +PAN -UAO -TCO -DIT +SSBS BTYPE=--)
pc : kfree+0x54/0x2d8
lr : xlog_cil_committed+0x11c/0x1d8 [xfs]
sp : fffffe00830cfbe0
x29: fffffe00830cfbe0 x28: fffffc00240e0c80 x27: fffffc00240e0c00
x26: 00000005000037a8 x25: 0000000000000000 x24: 0000000000000000
x23: fffffc0021e68d40 x22: fffffe00818e0000 x21: fffffc0021e68d88
x20: fffffe007a6b93cc x19: ffffffff80206380 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000 x15: fffffe008840f620
x14: 0000000000000000 x13: 0000000000000020 x12: 0101010101010101
x11: 0000000000000040 x10: fffffc0025b0d5d8 x9 : fffffe007a6b93cc
x8 : fffffe00830cfbe0 x7 : 0000000000000000 x6 : 0000000000000000
x5 : d230261c49c51c03 x4 : fffffc00e1357340 x3 : dead000000000122
x2 : fffffc00ea7fa000 x1 : fffffc0021e68d88 x0 : ffffffff00000000
Call trace:
kfree+0x54/0x2d8
xlog_cil_committed+0x11c/0x1d8 [xfs 6eb07a1ebfe13a228ea62c550c04c138eaa0de6a]
xlog_cil_process_committed+0x6c/0xa8 [xfs 6eb07a1ebfe13a228ea62c550c04c138eaa0de6a]
xlog_state_do_callback+0x1e0/0x3e0 [xfs 6eb07a1ebfe13a228ea62c550c04c138eaa0de6a]
xlog_state_done_syncing+0x8c/0x158 [xfs 6eb07a1ebfe13a228ea62c550c04c138eaa0de6a]
xlog_ioend_work+0x70/0xd8 [xfs 6eb07a1ebfe13a228ea62c550c04c138eaa0de6a]
process_one_work+0x174/0x3e8
worker_thread+0x2c4/0x3e8
kthread+0x110/0x128
ret_from_fork+0x10/0x20
Code: 8b1302d3 b2607fe0 d350fe73 8b131813 (f9400660)
---[ end trace 0000000000000000 ]---
next reply other threads:[~2024-02-24 1:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 1:02 Darrick J. Wong [this message]
2024-02-24 1:29 ` [GIT PULL 1/18] xfs: repair inode mode by scanning dirs Darrick J. Wong
2024-02-24 1:29 ` [GIT PULL 2/18] xfs: online repair of quota counters Darrick J. Wong
2024-02-24 1:29 ` [GIT PULL 3/18] xfs: online repair of file link counts Darrick J. Wong
2024-02-24 1:29 ` [GIT PULL 4/18] xfs: report corruption to the health trackers Darrick J. Wong
2024-02-24 1:30 ` [GIT PULL 5/18] xfs: indirect health reporting Darrick J. Wong
2024-02-24 1:30 ` [GIT PULL 6/18] xfs: online repair for fs summary counters Darrick J. Wong
2024-02-24 1:30 ` [GIT PULL 7/18] xfs: move btree geometry to ops struct Darrick J. Wong
2024-02-24 1:31 ` [GIT PULL 8/18] xfs: remove bc_btnum from btree cursors Darrick J. Wong
2024-02-24 1:31 ` [GIT PULL 9/18] xfs: btree check cleanups Darrick J. Wong
2024-02-24 1:31 ` [GIT PULL 10/18] xfs: btree readahead cleanups Darrick J. Wong
2024-02-24 1:31 ` [GIT PULL 11/18] xfs: buftarg cleanups Darrick J. Wong
2024-02-24 1:32 ` [GIT PULL 12/18] xfs: support in-memory btrees Darrick J. Wong
2024-02-24 1:32 ` [GIT PULL 13/18] xfs: online repair of rmap btrees Darrick J. Wong
2024-02-24 1:32 ` [GIT PULL 14/18] xfs: reduce refcount repair memory usage Darrick J. Wong
2024-02-24 1:32 ` [GIT PULL 15/18] xfs: bmap log intent cleanups Darrick J. Wong
2024-02-24 1:33 ` [GIT PULL 16/18] xfs: widen BUI formats to support realtime Darrick J. Wong
2024-02-24 1:33 ` [GIT PULL 17/18] xfs: support attrfork and unwritten BUIs Darrick J. Wong
2024-02-24 1:33 ` [GIT PULL 18/18] xfs: clean up symbolic link code Darrick J. Wong
2024-02-25 12:51 ` [PRBOMB] xfs: online repair patches for 6.9 Chandan Babu R
2024-02-26 10:26 ` Christoph Hellwig
2024-02-26 12:53 ` Dave Chinner
2024-02-26 12:59 ` Chandan Babu R
2024-02-26 13:04 ` Chandan Babu R
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=20240224010220.GN6226@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=chandanrlinux@gmail.com \
--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