On 2/17/23 4:45 PM, shrikanth hegde wrote: > We are observing panic on boot upon loading the latest stable tree(v6.2-rc4) in > one of our systems. System fails to come up. System was booting well > with v5.17, v5.19 kernel. We started seeing this issue when loading v6.0 kernel. > > Panic Log is below. > [ 333.390539] ------------[ cut here ]------------ > [ 333.390552] WARNING: CPU: 56 PID: 12450 at fs/xfs/xfs_inode.c:1839 xfs_iunlink_lookup+0x58/0x80 [xfs] > > we did a git bisect between 5.17 and 6.0. Bisect points to commit 04755d2e5821 > as the bad commit. > Short description of commit: > commit 04755d2e5821b3afbaadd09fe5df58d04de36484 (refs/bisect/bad) > Author: Dave Chinner <dchinner@xxxxxxxxxx> > Date: Thu Jul 14 11:42:39 2022 +1000 > > xfs: refactor xlog_recover_process_iunlinks() > > Tried one of the recent patch sent by Dave. https://lore.kernel.org/all/20230118224505.1964941-1-david@xxxxxxxxxxxxx/ If the full series is applied, it panics upon booting. i.e same problem persists. If only "[6/42] xfs: don't assert fail on transaction cancel with deferred ops" is applied, then it doesnt panic at boot. It panics later, when doing a make. A bit better than not booting. But still panics later.
