Re: WARN_ON in __writeback_inodes_sb_nr

2017-12-20 Thread Nikolay Borisov 


On 20.12.2017 21:16, David Ahern wrote:
> I am still seeing this problem on 4.15.0-rc3

This is a known problem and the offending commit is this one
ce8ea7cc6eb3 ("btrfs: don't call btrfs_start_delalloc_roots in
flushoncommit") and this manifests only if you have mounted with
flushoncommit mount option. A fix is unlikely to land for 4.15
> 
> 
> On 11/17/17 12:55 PM, David Ahern wrote:
>> I see a backtrace booting 4.14+ on a mellanox switch. The trace is due
>> to the WARN_ON in __writeback_inodes_sb_nr.
>>
>> [   40.958590] WARNING: CPU: 0 PID: 183 at
>> /home/dsa/kernel-2.git/fs/fs-writeback.c:2339
>> __writeback_inodes_sb_nr+0x8a/0x90
>> [   40.958593] Modules linked in: ebtable_filter ebtables ip6table_raw
>> ip6table_mangle ip6table_filter ip6_tables iTCO_wdt iTCO_vendor_support
>> coretemp x86_pkg_temp_thermal kvm_intel kvm irqbypass lpc_ich mfd_core
>> battery mei_me mei shpchp lm75 regmap_i2c pmbus pmbus_core i2c_dev
>> i2c_mux k10temp mpls_iptunnel mpls_router ip_tunnel at24 tun
>> br_netfilter bonding loop autofs4 dm_mod dax crc32c_intel i2c_i801
>> i2c_core thermal mlxsw_spectrum psample parman bridge stp llc mlxsw_pci
>> mlxsw_core mlxfw devlink e1000e hwmon
>> [   40.958664] CPU: 0 PID: 183 Comm: btrfs-transacti Not tainted 4.14.0+ #38
>> [   40.958666] Hardware name: Mellanox Technologies Ltd. Mellanox
>> switch/Mellanox switch, BIOS 4.6.5 05/21/2015
>> [   40.958669] task: 8803db266540 task.stack: c9344000
>> [   40.958675] RIP: 0010:__writeback_inodes_sb_nr+0x8a/0x90
>> [   40.958677] RSP: 0018:c9347dc8 EFLAGS: 00010246
>> [   40.958681] RAX:  RBX: 88040a641800 RCX:
>> 
>> [   40.958683] RDX: 0002 RSI: 45a7 RDI:
>> c9347e10
>> [   40.958685] RBP: c9347e20 R08: 0003 R09:
>> c9347dd0
>> [   40.958687] R10: 8803db287000 R11:  R12:
>> c9347dcc
>> [   40.958689] R13: 8804015e7a00 R14: 8803dade2bc8 R15:
>> 880400a68000
>> [   40.958692] FS:  () GS:88041dc0()
>> knlGS:
>> [   40.958695] CS:  0010 DS:  ES:  CR0: 80050033
>> [   40.958697] CR2: 5602d78aad50 CR3: 01e09002 CR4:
>> 001606f0
>> [   40.958699] Call Trace:
>> [   40.958710]  writeback_inodes_sb+0x27/0x30
>> [   40.958719]  btrfs_commit_transaction+0x7b2/0x8e0
>> [   40.958723]  ? start_transaction+0x9e/0x450
>> [   40.958728]  transaction_kthread+0x177/0x1b0
>> [   40.958735]  kthread+0x11d/0x150
>> [   40.958740]  ? btrfs_cleanup_transaction+0x4f0/0x4f0
>> [   40.958744]  ? kthread_associate_blkcg+0xb0/0xb0
>> [   40.958751]  ret_from_fork+0x24/0x30
>> [   40.958754] Code: 8b 42 70 48 85 c0 74 23 4c 89 ce 48 89 df 41 0f b6
>> d3 e8 fa fc ff ff 4c 89 e6 48 89 df e8 8f de ff ff 48 83 c4 48 5b 41 5c
>> 5d c3 <0f> ff eb d9 66 90 0f 1f 44 00 00 55 31 c9 48 89 e5 e8 60 ff ff
>> [   40.958826] ---[ end trace defabeb7afdfd414 ]---
>>
>>
>> Tree is DaveM's net-next, but it was recently merged with Linus' tree at:
>>
>> commit 6363b3f3ac5be096d08c8c504128befa0c033529
>> Merge: 1b6115fbe3b3 6297fabd93f9
>> Author: Linus Torvalds <torva...@linux-foundation.org>
>> Date:   Wed Nov 15 15:12:28 2017 -0800
>>
>> Merge tag 'ipmi-for-4.15' of git://github.com/cminyard/linux-ipmi
>>
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: WARN_ON in __writeback_inodes_sb_nr

2017-12-20 Thread David Ahern 
I am still seeing this problem on 4.15.0-rc3


On 11/17/17 12:55 PM, David Ahern wrote:
> I see a backtrace booting 4.14+ on a mellanox switch. The trace is due
> to the WARN_ON in __writeback_inodes_sb_nr.
> 
> [   40.958590] WARNING: CPU: 0 PID: 183 at
> /home/dsa/kernel-2.git/fs/fs-writeback.c:2339
> __writeback_inodes_sb_nr+0x8a/0x90
> [   40.958593] Modules linked in: ebtable_filter ebtables ip6table_raw
> ip6table_mangle ip6table_filter ip6_tables iTCO_wdt iTCO_vendor_support
> coretemp x86_pkg_temp_thermal kvm_intel kvm irqbypass lpc_ich mfd_core
> battery mei_me mei shpchp lm75 regmap_i2c pmbus pmbus_core i2c_dev
> i2c_mux k10temp mpls_iptunnel mpls_router ip_tunnel at24 tun
> br_netfilter bonding loop autofs4 dm_mod dax crc32c_intel i2c_i801
> i2c_core thermal mlxsw_spectrum psample parman bridge stp llc mlxsw_pci
> mlxsw_core mlxfw devlink e1000e hwmon
> [   40.958664] CPU: 0 PID: 183 Comm: btrfs-transacti Not tainted 4.14.0+ #38
> [   40.958666] Hardware name: Mellanox Technologies Ltd. Mellanox
> switch/Mellanox switch, BIOS 4.6.5 05/21/2015
> [   40.958669] task: 8803db266540 task.stack: c9344000
> [   40.958675] RIP: 0010:__writeback_inodes_sb_nr+0x8a/0x90
> [   40.958677] RSP: 0018:c9347dc8 EFLAGS: 00010246
> [   40.958681] RAX:  RBX: 88040a641800 RCX:
> 
> [   40.958683] RDX: 0002 RSI: 45a7 RDI:
> c9347e10
> [   40.958685] RBP: c9347e20 R08: 0003 R09:
> c9347dd0
> [   40.958687] R10: 8803db287000 R11:  R12:
> c9347dcc
> [   40.958689] R13: 8804015e7a00 R14: 8803dade2bc8 R15:
> 880400a68000
> [   40.958692] FS:  () GS:88041dc0()
> knlGS:
> [   40.958695] CS:  0010 DS:  ES:  CR0: 80050033
> [   40.958697] CR2: 5602d78aad50 CR3: 01e09002 CR4:
> 001606f0
> [   40.958699] Call Trace:
> [   40.958710]  writeback_inodes_sb+0x27/0x30
> [   40.958719]  btrfs_commit_transaction+0x7b2/0x8e0
> [   40.958723]  ? start_transaction+0x9e/0x450
> [   40.958728]  transaction_kthread+0x177/0x1b0
> [   40.958735]  kthread+0x11d/0x150
> [   40.958740]  ? btrfs_cleanup_transaction+0x4f0/0x4f0
> [   40.958744]  ? kthread_associate_blkcg+0xb0/0xb0
> [   40.958751]  ret_from_fork+0x24/0x30
> [   40.958754] Code: 8b 42 70 48 85 c0 74 23 4c 89 ce 48 89 df 41 0f b6
> d3 e8 fa fc ff ff 4c 89 e6 48 89 df e8 8f de ff ff 48 83 c4 48 5b 41 5c
> 5d c3 <0f> ff eb d9 66 90 0f 1f 44 00 00 55 31 c9 48 89 e5 e8 60 ff ff
> [   40.958826] ---[ end trace defabeb7afdfd414 ]---
> 
> 
> Tree is DaveM's net-next, but it was recently merged with Linus' tree at:
> 
> commit 6363b3f3ac5be096d08c8c504128befa0c033529
> Merge: 1b6115fbe3b3 6297fabd93f9
> Author: Linus Torvalds <torva...@linux-foundation.org>
> Date:   Wed Nov 15 15:12:28 2017 -0800
> 
> Merge tag 'ipmi-for-4.15' of git://github.com/cminyard/linux-ipmi
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: WARN_ON in __writeback_inodes_sb_nr when btrfs mounted with flushoncommit

2017-12-14 Thread Dmitrii Tcvetkov 
On Thu, 14 Dec 2017 15:21:52 +0200
Nikolay Borisov  wrote:

> On 14.12.2017 13:02, Dmitrii Tcvetkov wrote:
> > Since 4.15-rc1 if btrfs filesystem is mounted with flushoncommit mount
> > option then during fsync this trace appears in dmesg:
> > 
> > [   17.323092] WARNING: CPU: 0 PID: 364 at fs/fs-writeback.c:2339
> > __writeback_inodes_sb_nr+0xbf/0xd0 [   17.323925] Modules linked in:
> > [   17.324697] CPU: 0 PID: 364 Comm: systemd-journal Not tainted 4.15.0-rc3
> > #2 [   17.325424] Hardware name: To be filled by O.E.M. To be filled by
> > O.E.M./SABERTOOTH 990FX R2.0, BIOS 2901 05/04/2016 [   17.326177] RIP:
> > 0010:__writeback_inodes_sb_nr+0xbf/0xd0 [   17.326875] RSP:
> > 0018:8bcd40a77d08 EFLAGS: 00010246 [   17.327598] RAX: 
> > RBX: 8a3fa9764488 RCX:  [   17.328321] RDX:
> > 0002 RSI: 18ae RDI: 8a3fa96c7070 [   17.329012]
> > RBP: 8bcd40a77d0c R08: ff80 R09: 00ff
> > [   17.329740] R10: 8bcd40a77c10 R11: 1000 R12:
> >  [   17.330439] R13: 8a3fa915e698 R14: 8a3fb04ed780
> > R15: 8a3fa9a16610 [   17.331169] FS:  7f72d53338c0()
> > GS:8a3fbec0() knlGS: [   17.331880] CS:  0010
> > DS:  ES:  CR0: 80050033 [   17.332624] CR2:
> > 7f72d09a5000 CR3: 000329334000 CR4: 000406f0 [   17.83]
> > Call Trace: [   17.334113]  btrfs_commit_transaction+0x857/0x920
> > [   17.334874]  btrfs_sync_file+0x30c/0x3e0 [   17.335622]
> > do_fsync+0x33/0x60 [   17.336332]  SyS_fsync+0x7/0x10
> > [   17.337069]  do_syscall_64+0x63/0x360
> > [   17.337776]  entry_SYSCALL64_slow_path+0x25/0x25
> > [   17.338513] RIP: 0033:0x7f72d4f29094
> > [   17.339244] RSP: 002b:7ffd71b078f8 EFLAGS: 0246 ORIG_RAX:
> > 004a [   17.339962] RAX: ffda RBX: 
> > RCX: 7f72d4f29094 [   17.340718] RDX: 0009 RSI:
> > 5630b6f8b090 RDI: 0010 [   17.341431] RBP: 5630b6f8b090
> > R08: 000f R09:  [   17.342169] R10:
> >  R11: 0246 R12: 0010 [   17.342902]
> > R13: 5630b6f88f60 R14: 0001 R15: 0001
> > [   17.343604] Code: df 0f b6 d1 e8 a3 fc ff ff 48 89 ee 48 89 df e8 78 f5
> > ff ff 48 8b 44 24 48 65 48 33 04 25 28 00 00 00 75 0b 48 83 c4 50 5b 5d c3
> > <0f> ff eb ca e8 38 1e ec ff 0f 1f 84 00 00 00 00 00 41 54 55 48
> > [   17.344408] ---[ end trace ff4cf41ec70ec0a7 ]---  
> 
> So this is due to writeback_inodes_sb being called without holding
> s_umount. So 4.15-rc1 the first kernel that started exhibiting this or
> did you also see it with earlier kernel
>

I didn't test kernels during merge window, the behavior was since 4.15-rc1 and
it's relevant until current mainline. Can't reproduce on 4.14 and earlier.


--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: WARN_ON in __writeback_inodes_sb_nr when btrfs mounted with flushoncommit

2017-12-14 Thread David Sterba 
On Thu, Dec 14, 2017 at 03:21:52PM +0200, Nikolay Borisov wrote:
> 
> 
> On 14.12.2017 13:02, Dmitrii Tcvetkov wrote:
> > Since 4.15-rc1 if btrfs filesystem is mounted with flushoncommit mount 
> > option
> > then during fsync this trace appears in dmesg:
> > 
> > [   17.323092] WARNING: CPU: 0 PID: 364 at fs/fs-writeback.c:2339 
> > __writeback_inodes_sb_nr+0xbf/0xd0
> > [   17.323925] Modules linked in:
> > [   17.324697] CPU: 0 PID: 364 Comm: systemd-journal Not tainted 4.15.0-rc3 
> > #2
> > [   17.325424] Hardware name: To be filled by O.E.M. To be filled by 
> > O.E.M./SABERTOOTH 990FX R2.0, BIOS 2901 05/04/2016
> > [   17.326177] RIP: 0010:__writeback_inodes_sb_nr+0xbf/0xd0
> > [   17.326875] RSP: 0018:8bcd40a77d08 EFLAGS: 00010246
> > [   17.327598] RAX:  RBX: 8a3fa9764488 RCX: 
> > 
> > [   17.328321] RDX: 0002 RSI: 18ae RDI: 
> > 8a3fa96c7070
> > [   17.329012] RBP: 8bcd40a77d0c R08: ff80 R09: 
> > 00ff
> > [   17.329740] R10: 8bcd40a77c10 R11: 1000 R12: 
> > 
> > [   17.330439] R13: 8a3fa915e698 R14: 8a3fb04ed780 R15: 
> > 8a3fa9a16610
> > [   17.331169] FS:  7f72d53338c0() GS:8a3fbec0() 
> > knlGS:
> > [   17.331880] CS:  0010 DS:  ES:  CR0: 80050033
> > [   17.332624] CR2: 7f72d09a5000 CR3: 000329334000 CR4: 
> > 000406f0
> > [   17.83] Call Trace:
> > [   17.334113]  btrfs_commit_transaction+0x857/0x920
> > [   17.334874]  btrfs_sync_file+0x30c/0x3e0
> > [   17.335622]  do_fsync+0x33/0x60
> > [   17.336332]  SyS_fsync+0x7/0x10
> > [   17.337069]  do_syscall_64+0x63/0x360
> > [   17.337776]  entry_SYSCALL64_slow_path+0x25/0x25
> > [   17.338513] RIP: 0033:0x7f72d4f29094
> > [   17.339244] RSP: 002b:7ffd71b078f8 EFLAGS: 0246 ORIG_RAX: 
> > 004a
> > [   17.339962] RAX: ffda RBX:  RCX: 
> > 7f72d4f29094
> > [   17.340718] RDX: 0009 RSI: 5630b6f8b090 RDI: 
> > 0010
> > [   17.341431] RBP: 5630b6f8b090 R08: 000f R09: 
> > 
> > [   17.342169] R10:  R11: 0246 R12: 
> > 0010
> > [   17.342902] R13: 5630b6f88f60 R14: 0001 R15: 
> > 0001
> > [   17.343604] Code: df 0f b6 d1 e8 a3 fc ff ff 48 89 ee 48 89 df e8 78 f5 
> > ff
> > ff 48 8b 44 24 48 65 48 33 04 25 28 00 00 00 75 0b 48 83 c4 50 5b 5d c3 
> > <0f> ff
> > eb ca e8 38 1e ec ff 0f 1f 84 00 00 00 00 00 41 54 55 48
> > [   17.344408] ---[ end trace ff4cf41ec70ec0a7 ]---
> 
> So this is due to writeback_inodes_sb being called without holding
> s_umount. So 4.15-rc1 the first kernel that started exhibiting this or
> did you also see it with earlier kernel

This is new in 4.15, there was an earlier report
https://marc.info/?l=linux-btrfs=151315564008773
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: WARN_ON in __writeback_inodes_sb_nr when btrfs mounted with flushoncommit

2017-12-14 Thread Nikolay Borisov 


On 14.12.2017 13:02, Dmitrii Tcvetkov wrote:
> Since 4.15-rc1 if btrfs filesystem is mounted with flushoncommit mount option
> then during fsync this trace appears in dmesg:
> 
> [   17.323092] WARNING: CPU: 0 PID: 364 at fs/fs-writeback.c:2339 
> __writeback_inodes_sb_nr+0xbf/0xd0
> [   17.323925] Modules linked in:
> [   17.324697] CPU: 0 PID: 364 Comm: systemd-journal Not tainted 4.15.0-rc3 #2
> [   17.325424] Hardware name: To be filled by O.E.M. To be filled by 
> O.E.M./SABERTOOTH 990FX R2.0, BIOS 2901 05/04/2016
> [   17.326177] RIP: 0010:__writeback_inodes_sb_nr+0xbf/0xd0
> [   17.326875] RSP: 0018:8bcd40a77d08 EFLAGS: 00010246
> [   17.327598] RAX:  RBX: 8a3fa9764488 RCX: 
> 
> [   17.328321] RDX: 0002 RSI: 18ae RDI: 
> 8a3fa96c7070
> [   17.329012] RBP: 8bcd40a77d0c R08: ff80 R09: 
> 00ff
> [   17.329740] R10: 8bcd40a77c10 R11: 1000 R12: 
> 
> [   17.330439] R13: 8a3fa915e698 R14: 8a3fb04ed780 R15: 
> 8a3fa9a16610
> [   17.331169] FS:  7f72d53338c0() GS:8a3fbec0() 
> knlGS:
> [   17.331880] CS:  0010 DS:  ES:  CR0: 80050033
> [   17.332624] CR2: 7f72d09a5000 CR3: 000329334000 CR4: 
> 000406f0
> [   17.83] Call Trace:
> [   17.334113]  btrfs_commit_transaction+0x857/0x920
> [   17.334874]  btrfs_sync_file+0x30c/0x3e0
> [   17.335622]  do_fsync+0x33/0x60
> [   17.336332]  SyS_fsync+0x7/0x10
> [   17.337069]  do_syscall_64+0x63/0x360
> [   17.337776]  entry_SYSCALL64_slow_path+0x25/0x25
> [   17.338513] RIP: 0033:0x7f72d4f29094
> [   17.339244] RSP: 002b:7ffd71b078f8 EFLAGS: 0246 ORIG_RAX: 
> 004a
> [   17.339962] RAX: ffda RBX:  RCX: 
> 7f72d4f29094
> [   17.340718] RDX: 0009 RSI: 5630b6f8b090 RDI: 
> 0010
> [   17.341431] RBP: 5630b6f8b090 R08: 000f R09: 
> 
> [   17.342169] R10:  R11: 0246 R12: 
> 0010
> [   17.342902] R13: 5630b6f88f60 R14: 0001 R15: 
> 0001
> [   17.343604] Code: df 0f b6 d1 e8 a3 fc ff ff 48 89 ee 48 89 df e8 78 f5 ff
> ff 48 8b 44 24 48 65 48 33 04 25 28 00 00 00 75 0b 48 83 c4 50 5b 5d c3 <0f> 
> ff
> eb ca e8 38 1e ec ff 0f 1f 84 00 00 00 00 00 41 54 55 48
> [   17.344408] ---[ end trace ff4cf41ec70ec0a7 ]---

So this is due to writeback_inodes_sb being called without holding
s_umount. So 4.15-rc1 the first kernel that started exhibiting this or
did you also see it with earlier kernel

> 
> If fs mounted without flushoncommit then no warnings. Other mount options 
> don't influence the behaviour.
> 
> Steps to reproduce:
> mkfs.btrfs 
> mount -o flushoncommit  
> echo test > /test 
> btrfs filesystem sync 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARN_ON in __writeback_inodes_sb_nr when btrfs mounted with flushoncommit

2017-12-14 Thread Dmitrii Tcvetkov 
Since 4.15-rc1 if btrfs filesystem is mounted with flushoncommit mount option
then during fsync this trace appears in dmesg:

[   17.323092] WARNING: CPU: 0 PID: 364 at fs/fs-writeback.c:2339 
__writeback_inodes_sb_nr+0xbf/0xd0
[   17.323925] Modules linked in:
[   17.324697] CPU: 0 PID: 364 Comm: systemd-journal Not tainted 4.15.0-rc3 #2
[   17.325424] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./SABERTOOTH 990FX R2.0, BIOS 2901 05/04/2016
[   17.326177] RIP: 0010:__writeback_inodes_sb_nr+0xbf/0xd0
[   17.326875] RSP: 0018:8bcd40a77d08 EFLAGS: 00010246
[   17.327598] RAX:  RBX: 8a3fa9764488 RCX: 
[   17.328321] RDX: 0002 RSI: 18ae RDI: 8a3fa96c7070
[   17.329012] RBP: 8bcd40a77d0c R08: ff80 R09: 00ff
[   17.329740] R10: 8bcd40a77c10 R11: 1000 R12: 
[   17.330439] R13: 8a3fa915e698 R14: 8a3fb04ed780 R15: 8a3fa9a16610
[   17.331169] FS:  7f72d53338c0() GS:8a3fbec0() 
knlGS:
[   17.331880] CS:  0010 DS:  ES:  CR0: 80050033
[   17.332624] CR2: 7f72d09a5000 CR3: 000329334000 CR4: 000406f0
[   17.83] Call Trace:
[   17.334113]  btrfs_commit_transaction+0x857/0x920
[   17.334874]  btrfs_sync_file+0x30c/0x3e0
[   17.335622]  do_fsync+0x33/0x60
[   17.336332]  SyS_fsync+0x7/0x10
[   17.337069]  do_syscall_64+0x63/0x360
[   17.337776]  entry_SYSCALL64_slow_path+0x25/0x25
[   17.338513] RIP: 0033:0x7f72d4f29094
[   17.339244] RSP: 002b:7ffd71b078f8 EFLAGS: 0246 ORIG_RAX: 
004a
[   17.339962] RAX: ffda RBX:  RCX: 7f72d4f29094
[   17.340718] RDX: 0009 RSI: 5630b6f8b090 RDI: 0010
[   17.341431] RBP: 5630b6f8b090 R08: 000f R09: 
[   17.342169] R10:  R11: 0246 R12: 0010
[   17.342902] R13: 5630b6f88f60 R14: 0001 R15: 0001
[   17.343604] Code: df 0f b6 d1 e8 a3 fc ff ff 48 89 ee 48 89 df e8 78 f5 ff
ff 48 8b 44 24 48 65 48 33 04 25 28 00 00 00 75 0b 48 83 c4 50 5b 5d c3 <0f> ff
eb ca e8 38 1e ec ff 0f 1f 84 00 00 00 00 00 41 54 55 48
[   17.344408] ---[ end trace ff4cf41ec70ec0a7 ]---

If fs mounted without flushoncommit then no warnings. Other mount options don't 
influence the behaviour.

Steps to reproduce:
mkfs.btrfs 
mount -o flushoncommit  
echo test > /test 
btrfs filesystem sync 
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARN_ON in __writeback_inodes_sb_nr

2017-11-17 Thread David Ahern 
I see a backtrace booting 4.14+ on a mellanox switch. The trace is due
to the WARN_ON in __writeback_inodes_sb_nr.

[   40.958590] WARNING: CPU: 0 PID: 183 at
/home/dsa/kernel-2.git/fs/fs-writeback.c:2339
__writeback_inodes_sb_nr+0x8a/0x90
[   40.958593] Modules linked in: ebtable_filter ebtables ip6table_raw
ip6table_mangle ip6table_filter ip6_tables iTCO_wdt iTCO_vendor_support
coretemp x86_pkg_temp_thermal kvm_intel kvm irqbypass lpc_ich mfd_core
battery mei_me mei shpchp lm75 regmap_i2c pmbus pmbus_core i2c_dev
i2c_mux k10temp mpls_iptunnel mpls_router ip_tunnel at24 tun
br_netfilter bonding loop autofs4 dm_mod dax crc32c_intel i2c_i801
i2c_core thermal mlxsw_spectrum psample parman bridge stp llc mlxsw_pci
mlxsw_core mlxfw devlink e1000e hwmon
[   40.958664] CPU: 0 PID: 183 Comm: btrfs-transacti Not tainted 4.14.0+ #38
[   40.958666] Hardware name: Mellanox Technologies Ltd. Mellanox
switch/Mellanox switch, BIOS 4.6.5 05/21/2015
[   40.958669] task: 8803db266540 task.stack: c9344000
[   40.958675] RIP: 0010:__writeback_inodes_sb_nr+0x8a/0x90
[   40.958677] RSP: 0018:c9347dc8 EFLAGS: 00010246
[   40.958681] RAX:  RBX: 88040a641800 RCX:

[   40.958683] RDX: 0002 RSI: 45a7 RDI:
c9347e10
[   40.958685] RBP: c9347e20 R08: 0003 R09:
c9347dd0
[   40.958687] R10: 8803db287000 R11:  R12:
c9347dcc
[   40.958689] R13: 8804015e7a00 R14: 8803dade2bc8 R15:
880400a68000
[   40.958692] FS:  () GS:88041dc0()
knlGS:
[   40.958695] CS:  0010 DS:  ES:  CR0: 80050033
[   40.958697] CR2: 5602d78aad50 CR3: 01e09002 CR4:
001606f0
[   40.958699] Call Trace:
[   40.958710]  writeback_inodes_sb+0x27/0x30
[   40.958719]  btrfs_commit_transaction+0x7b2/0x8e0
[   40.958723]  ? start_transaction+0x9e/0x450
[   40.958728]  transaction_kthread+0x177/0x1b0
[   40.958735]  kthread+0x11d/0x150
[   40.958740]  ? btrfs_cleanup_transaction+0x4f0/0x4f0
[   40.958744]  ? kthread_associate_blkcg+0xb0/0xb0
[   40.958751]  ret_from_fork+0x24/0x30
[   40.958754] Code: 8b 42 70 48 85 c0 74 23 4c 89 ce 48 89 df 41 0f b6
d3 e8 fa fc ff ff 4c 89 e6 48 89 df e8 8f de ff ff 48 83 c4 48 5b 41 5c
5d c3 <0f> ff eb d9 66 90 0f 1f 44 00 00 55 31 c9 48 89 e5 e8 60 ff ff
[   40.958826] ---[ end trace defabeb7afdfd414 ]---


Tree is DaveM's net-next, but it was recently merged with Linus' tree at:

commit 6363b3f3ac5be096d08c8c504128befa0c033529
Merge: 1b6115fbe3b3 6297fabd93f9
Author: Linus Torvalds <torva...@linux-foundation.org>
Date:   Wed Nov 15 15:12:28 2017 -0800

Merge tag 'ipmi-for-4.15' of git://github.com/cminyard/linux-ipmi

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html