Re: xfs: list corruption in xfs_setup_inode()

2018-03-20 Thread Cong Wang
On Mon, Mar 19, 2018 at 4:39 PM, Dave Chinner wrote: > On Mon, Mar 19, 2018 at 02:37:22PM -0700, Cong Wang wrote: >> On Mon, Oct 30, 2017 at 2:55 PM, Cong Wang wrote: >> > Hello, >> > >> > We triggered a list corruption (double add) warning below on our 4.9 >> > kernel (the 4.9 kernel we use is b

Re: xfs: list corruption in xfs_setup_inode()

2018-03-19 Thread Dave Chinner
On Mon, Mar 19, 2018 at 02:37:22PM -0700, Cong Wang wrote: > On Mon, Oct 30, 2017 at 2:55 PM, Cong Wang wrote: > > Hello, > > > > We triggered a list corruption (double add) warning below on our 4.9 > > kernel (the 4.9 kernel we use is based on -stable release, with only a > > few unrelated networ

Re: xfs: list corruption in xfs_setup_inode()

2018-03-19 Thread Cong Wang
On Mon, Oct 30, 2017 at 2:55 PM, Cong Wang wrote: > Hello, > > We triggered a list corruption (double add) warning below on our 4.9 > kernel (the 4.9 kernel we use is based on -stable release, with only a > few unrelated networking backports): We still keep getting this warning on 4.9 kernel. Loo

Re: xfs: list corruption in xfs_setup_inode()

2017-11-01 Thread Cong Wang
On Wed, Nov 1, 2017 at 2:32 PM, Dave Chinner wrote: > On Wed, Nov 01, 2017 at 04:07:01PM +1100, Dave Chinner wrote: >> On Tue, Oct 31, 2017 at 09:43:03PM -0700, Cong Wang wrote: >> > On Tue, Oct 31, 2017 at 8:05 PM, Dave Chinner wrote: >> > > On Tue, Oct 31, 2017 at 06:51:08PM -0700, Cong Wang wr

Re: xfs: list corruption in xfs_setup_inode()

2017-11-01 Thread Dave Chinner
On Wed, Nov 01, 2017 at 04:07:01PM +1100, Dave Chinner wrote: > On Tue, Oct 31, 2017 at 09:43:03PM -0700, Cong Wang wrote: > > On Tue, Oct 31, 2017 at 8:05 PM, Dave Chinner wrote: > > > On Tue, Oct 31, 2017 at 06:51:08PM -0700, Cong Wang wrote: > > >> >> Please let me know if I can provide any oth

Re: xfs: list corruption in xfs_setup_inode()

2017-11-01 Thread Christoph Hellwig
On Wed, Nov 01, 2017 at 04:07:01PM +1100, Dave Chinner wrote: > > We are trying to make kdump working, but even if kdump works > > we still can't turn on panic_on_warn since this is production > > machine. > > Hmmm. Ok, maybe you could leave a trace of the xfs_iget* trace > points running and chec

Re: xfs: list corruption in xfs_setup_inode()

2017-10-31 Thread Dave Chinner
On Tue, Oct 31, 2017 at 09:43:03PM -0700, Cong Wang wrote: > On Tue, Oct 31, 2017 at 8:05 PM, Dave Chinner wrote: > > On Tue, Oct 31, 2017 at 06:51:08PM -0700, Cong Wang wrote: > >> >> Please let me know if I can provide any other information. > >> > > >> > How do you reproduce the problem? > >> >

Re: xfs: list corruption in xfs_setup_inode()

2017-10-31 Thread Cong Wang
On Tue, Oct 31, 2017 at 8:05 PM, Dave Chinner wrote: > On Tue, Oct 31, 2017 at 06:51:08PM -0700, Cong Wang wrote: >> On Mon, Oct 30, 2017 at 5:33 PM, Dave Chinner wrote: >> > On Mon, Oct 30, 2017 at 02:55:43PM -0700, Cong Wang wrote: >> >> Hello, >> >> >> >> We triggered a list corruption (double

Re: xfs: list corruption in xfs_setup_inode()

2017-10-31 Thread Dave Chinner
On Tue, Oct 31, 2017 at 06:51:08PM -0700, Cong Wang wrote: > On Mon, Oct 30, 2017 at 5:33 PM, Dave Chinner wrote: > > On Mon, Oct 30, 2017 at 02:55:43PM -0700, Cong Wang wrote: > >> Hello, > >> > >> We triggered a list corruption (double add) warning below on our 4.9 > >> kernel (the 4.9 kernel we

Re: xfs: list corruption in xfs_setup_inode()

2017-10-31 Thread Cong Wang
On Mon, Oct 30, 2017 at 5:33 PM, Dave Chinner wrote: > On Mon, Oct 30, 2017 at 02:55:43PM -0700, Cong Wang wrote: >> Hello, >> >> We triggered a list corruption (double add) warning below on our 4.9 >> kernel (the 4.9 kernel we use is based on -stable release, with only a >> few unrelated networki

Re: xfs: list corruption in xfs_setup_inode()

2017-10-30 Thread Dave Chinner
On Mon, Oct 30, 2017 at 02:55:43PM -0700, Cong Wang wrote: > Hello, > > We triggered a list corruption (double add) warning below on our 4.9 > kernel (the 4.9 kernel we use is based on -stable release, with only a > few unrelated networking backports): > > > WARNING: CPU: 5 PID: 628 at lib/list_