You are not logged in.

#1 2022-12-27 21:48:55

aocab
Member
Registered: 2013-08-15
Posts: 33

[solved] system crash accessing cifs 1.0 shares

When I try to access the NAS share using Dolphin or Audacious I get the following in dmesg and the system will sometimes crash hard to the point nothing works except force turning it off at the power button.

[ 1919.124976] ------------[ cut here ]------------
[ 1919.124982] list_add corruption. prev->next should be next (ffff8948930bd6d0), but was 0000000000000000. (prev=ffffae4080bcbb80).
[ 1919.124994] WARNING: CPU: 0 PID: 3112 at lib/list_debug.c:30 __list_add_valid+0x83/0xa0
[ 1919.125003] Modules linked in: nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver fscache netfs snd_seq_dummy snd_seq snd_seq_device cfg80211 xt_tcpudp xt_LOG nf_log_syslog xt_limit xt_pkttype xt_conntrack iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nct6775 nct6775_core nf_defrag_ipv4 hwmon_vid libcrc32c iptable_mangle intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass joydev crct10dif_pclmul crc32_pclmul polyval_clmulni mousedev polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 aesni_intel snd_hda_codec_realtek snd_hda_codec_generic eeepc_wmi snd_hda_codec_hdmi spi_nor snd_hda_intel asus_wmi snd_intel_dspcfg crypto_simd mtd cryptd ledtrig_audio sparse_keymap rapl snd_intel_sdw_acpi spi_intel_platform platform_profile snd_hda_codec iTCO_wdt intel_cstate intel_uncore intel_pmc_bxt spi_intel rfkill at24 iTCO_vendor_support mei_pxp mei_hdcp snd_hda_core wmi_bmof pcspkr i2c_i801 snd_hwdep i2c_smbus snd_pcm e1000e
[ 1919.125059]  lpc_ich snd_timer snd mei_me soundcore mei mac_hid sg fuse crypto_user bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid i915 drm_buddy intel_gtt drm_display_helper sr_mod crc32c_intel cec xhci_pci cdrom xhci_pci_renesas ttm video wmi
[ 1919.125083] CPU: 0 PID: 3112 Comm: audacious Tainted: G      D W          6.1.1-arch1-1 #1 9bd09188b430be630e611f984454e4f3c489be77
[ 1919.125087] Hardware name: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD/K30AD_M31AD_M51AD_M32AD, BIOS 0802 08/03/2015
[ 1919.125089] RIP: 0010:__list_add_valid+0x83/0xa0
[ 1919.125093] Code: eb e9 48 89 c1 48 c7 c7 88 35 af a8 e8 41 32 64 00 0f 0b eb d6 48 89 d1 48 89 c6 4c 89 c2 48 c7 c7 d8 35 af a8 e8 28 32 64 00 <0f> 0b eb bd 48 89 f2 48 89 c1 48 89 fe 48 c7 c7 28 36 af a8 e8 0f
[ 1919.125095] RSP: 0018:ffffae4080fc3a90 EFLAGS: 00010282
[ 1919.125098] RAX: 0000000000000000 RBX: ffffae4080fc3b60 RCX: 0000000000000027
[ 1919.125100] RDX: ffff894997a21668 RSI: 0000000000000001 RDI: ffff894997a21660
[ 1919.125101] RBP: ffff8948930bd000 R08: 0000000000000000 R09: ffffae4080fc3918
[ 1919.125103] R10: 0000000000000003 R11: ffffffffa92cb768 R12: ffffae4080bcbb80
[ 1919.125104] R13: ffff8948930bd6d0 R14: ffff8948930bd000 R15: ffff89492909b300
[ 1919.125106] FS:  00007f6764ffd6c0(0000) GS:ffff894997a00000(0000) knlGS:0000000000000000
[ 1919.125109] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1919.125111] CR2: 00007f6754000020 CR3: 00000001b9570001 CR4: 00000000001706f0
[ 1919.125113] Call Trace:
[ 1919.125115]  <TASK>
[ 1919.125118]  cifs_add_pending_open_locked+0x51/0x80 [cifs d1264784e9b497a2054e5c37788e512b47d5272b]
[ 1919.125268]  cifs_add_pending_open+0x31/0x50 [cifs d1264784e9b497a2054e5c37788e512b47d5272b]
[ 1919.125395]  cifs_open+0x23d/0xb50 [cifs d1264784e9b497a2054e5c37788e512b47d5272b]
[ 1919.125521]  ? kmem_cache_free_bulk.part.0+0x510/0x630
[ 1919.125527]  ? open_cached_dir_by_dentry+0x56/0xf0 [cifs d1264784e9b497a2054e5c37788e512b47d5272b]
[ 1919.125654]  ? cifs_dentry_needs_reval+0xa9/0x1d0 [cifs d1264784e9b497a2054e5c37788e512b47d5272b]
[ 1919.125781]  ? cifs_get_readable_path+0x120/0x120 [cifs d1264784e9b497a2054e5c37788e512b47d5272b]
[ 1919.125905]  ? do_dentry_open+0x1e5/0x460
[ 1919.125910]  do_dentry_open+0x1e5/0x460
[ 1919.125914]  path_openat+0xdc6/0x1270
[ 1919.125920]  do_filp_open+0xb3/0x160
[ 1919.125926]  do_sys_openat2+0xaf/0x170
[ 1919.125931]  __x64_sys_openat+0x6e/0xa0
[ 1919.125935]  do_syscall_64+0x5f/0x90
[ 1919.125942]  ? exc_page_fault+0x74/0x170
[ 1919.125946]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 1919.125951] RIP: 0033:0x7f679490fde0
[ 1919.125967] Code: 48 89 44 24 20 75 97 44 89 54 24 0c e8 99 bf f8 ff 44 8b 54 24 0c 89 da 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 89 44 24 0c e8 ec bf f8 ff 8b 44
[ 1919.125969] RSP: 002b:00007f6764ffc840 EFLAGS: 00000293 ORIG_RAX: 0000000000000101
[ 1919.125972] RAX: ffffffffffffffda RBX: 0000000000080000 RCX: 00007f679490fde0
[ 1919.125974] RDX: 0000000000080000 RSI: 00007f67646fd0d0 RDI: 00000000ffffff9c
[ 1919.125975] RBP: 00007f67646fd0d0 R08: 0000000000000000 R09: 0000000000000001
[ 1919.125977] R10: 0000000000000000 R11: 0000000000000293 R12: 00007f67646fd0d0
[ 1919.125979] R13: 00007f67646fd168 R14: 0000000000000001 R15: 00007f6764ffca70
[ 1919.125982]  </TASK>
[ 1919.125984] ---[ end trace 0000000000000000 ]---
[ 1933.446380] general protection fault, probably for non-canonical address 0x1cd9ad000beed00: 0000 [#5] PREEMPT SMP PTI
[ 1933.446386] CPU: 3 PID: 3082 Comm: kioslave5 Tainted: G      D W          6.1.1-arch1-1 #1 9bd09188b430be630e611f984454e4f3c489be77
[ 1933.446389] Hardware name: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD/K30AD_M31AD_M51AD_M32AD, BIOS 0802 08/03/2015
[ 1933.446391] RIP: 0010:strlen+0x4/0x30
[ 1933.446395] Code: b6 07 38 d0 74 14 48 83 c7 01 84 c0 74 05 48 39 f7 75 ec 31 c0 c3 cc cc cc cc 48 89 f8 c3 cc cc cc cc 0f 1f 40 00 f3 0f 1e fa <80> 3f 00 74 14 48 89 f8 48 83 c0 01 80 38 00 75 f7 48 29 f8 c3 cc
[ 1933.446397] RSP: 0018:ffffae4080baba00 EFLAGS: 00010206
[ 1933.446399] RAX: 01cd9ad000beed00 RBX: 01cd9ad000beed00 RCX: 0000000000000001
[ 1933.446401] RDX: 0000000000000000 RSI: 0000000000000cc0 RDI: 01cd9ad000beed00
[ 1933.446402] RBP: ffff8949508d1f00 R08: 0000000000000040 R09: ffff8949508d1f00
[ 1933.446403] R10: ffff89494d8d1000 R11: 0000000000000000 R12: 0000000000000cc0
[ 1933.446405] R13: ffff894785d821c0 R14: ffff8948930bd000 R15: ffff89478642cc00
[ 1933.446406] FS:  00007f1ee240e880(0000) GS:ffff894997b80000(0000) knlGS:0000000000000000
[ 1933.446408] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1933.446409] CR2: 0000561392945da0 CR3: 0000000002278006 CR4: 00000000001706e0
[ 1933.446411] Call Trace:
[ 1933.446413]  <TASK>
[ 1933.446414]  kstrdup+0x1d/0x70
[ 1933.446420]  cifs_new_fileinfo+0xb8/0x520 [cifs d1264784e9b497a2054e5c37788e512b47d5272b]
[ 1933.446540]  cifs_open+0x6ab/0xb50 [cifs d1264784e9b497a2054e5c37788e512b47d5272b]
[ 1933.446630]  ? cifs_get_readable_path+0x120/0x120 [cifs d1264784e9b497a2054e5c37788e512b47d5272b]
[ 1933.446719]  ? do_dentry_open+0x1e5/0x460
[ 1933.446724]  do_dentry_open+0x1e5/0x460
[ 1933.446727]  path_openat+0xdc6/0x1270
[ 1933.446730]  do_filp_open+0xb3/0x160
[ 1933.446734]  do_sys_openat2+0xaf/0x170
[ 1933.446738]  __x64_sys_openat+0x6e/0xa0
[ 1933.446741]  do_syscall_64+0x5f/0x90
[ 1933.446746]  ? syscall_exit_to_user_mode+0x1b/0x40
[ 1933.446749]  ? do_syscall_64+0x6b/0x90
[ 1933.446752]  ? do_syscall_64+0x6b/0x90
[ 1933.446755]  ? syscall_exit_to_user_mode+0x1b/0x40
[ 1933.446757]  ? do_syscall_64+0x6b/0x90
[ 1933.446760]  ? syscall_exit_to_user_mode+0x1b/0x40
[ 1933.446762]  ? do_syscall_64+0x6b/0x90
[ 1933.446765]  ? do_syscall_64+0x6b/0x90
[ 1933.446768]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 1933.446772] RIP: 0033:0x7f1ee6f0fde0
[ 1933.446785] Code: 48 89 44 24 20 75 97 44 89 54 24 0c e8 99 bf f8 ff 44 8b 54 24 0c 89 da 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 89 44 24 0c e8 ec bf f8 ff 8b 44
[ 1933.446787] RSP: 002b:00007ffe25fe23f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000101
[ 1933.446789] RAX: ffffffffffffffda RBX: 0000000000080000 RCX: 00007f1ee6f0fde0
[ 1933.446790] RDX: 0000000000080000 RSI: 000056518d506148 RDI: 00000000ffffff9c
[ 1933.446792] RBP: 000056518d506148 R08: 0000000000000000 R09: 0000000000000100
[ 1933.446793] R10: 0000000000000000 R11: 0000000000000293 R12: 000056518d22c640
[ 1933.446794] R13: 0000000000000000 R14: 00007ffe25fe24a8 R15: 00007ffe25fe25d0
[ 1933.446797]  </TASK>
[ 1933.446798] Modules linked in: nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver fscache netfs snd_seq_dummy snd_seq snd_seq_device cfg80211 xt_tcpudp xt_LOG nf_log_syslog xt_limit xt_pkttype xt_conntrack iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nct6775 nct6775_core nf_defrag_ipv4 hwmon_vid libcrc32c iptable_mangle intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass joydev crct10dif_pclmul crc32_pclmul polyval_clmulni mousedev polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 aesni_intel snd_hda_codec_realtek snd_hda_codec_generic eeepc_wmi snd_hda_codec_hdmi spi_nor snd_hda_intel asus_wmi snd_intel_dspcfg crypto_simd mtd cryptd ledtrig_audio sparse_keymap rapl snd_intel_sdw_acpi spi_intel_platform platform_profile snd_hda_codec iTCO_wdt intel_cstate intel_uncore intel_pmc_bxt spi_intel rfkill at24 iTCO_vendor_support mei_pxp mei_hdcp snd_hda_core wmi_bmof pcspkr i2c_i801 snd_hwdep i2c_smbus snd_pcm e1000e
[ 1933.446843]  lpc_ich snd_timer snd mei_me soundcore mei mac_hid sg fuse crypto_user bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid i915 drm_buddy intel_gtt drm_display_helper sr_mod crc32c_intel cec xhci_pci cdrom xhci_pci_renesas ttm video wmi
[ 1933.446863] ---[ end trace 0000000000000000 ]---

My fstab entry looks like this:

//192.168.1.1/Music   /mnt/Music   cifs   vers=1.0,ro,users,noauto,username=guest,password=guest,iocharset=utf8,sec=ntlmv2  0  0

It was working fine but it has been a while since I accessed them in Arch.  The last time was probably before Arch got kernel 6.

I also tried installing the LTS kernel during this time but ended up messing things up so I went back to the default kernel 6.

It still works fine from Slackware current and Windows 10.  Just can't seem to figure out what broke.

I did come across this:
Bug 215375 - Unable to mount cifs 1.0 shares

And I'm reading through it to see if it is related or if I might get an idea of what else to check.

Anyway, if anyone has any ideas would you please point me in the right direction?

Thanks

edit: various other information

cat /proc/fs/cifs/DebugData

Display Internal CIFS Data Structures for Debugging
---------------------------------------------------
CIFS Version 2.40
Features: DFS,FSCACHE,STATS,DEBUG,ALLOW_INSECURE_LEGACY,CIFS_POSIX,UPCALL(SPNEGO),XATTR,ACL,WITNESS
CIFSMaxBufSize: 16384
Active VFS Requests: 3

Servers: 
1) ConnectionId: 0x1 Hostname: 192.168.1.1 
Number of credits: 50 Dialect 0x0
TCP status: 1 Instance: 1
Local Users To Server: 1 SecMode: 0x3 Req On Wire: 0
In Send: 0 In MaxReq Wait: 0

        Sessions: 
        1) Name: 192.168.1.1  Domain: WORKGROUP Uses: 1 OS: Unix 
        NOS: Samba 3.0.28a      Capability: 0x80f3fd
        SMB session status: 1 
        Security type: NTLMv2  SessionId: 0x64
        User: 0 Cred User: 0

        Shares: 
        0) IPC: \\192.168.1.1\IPC$ Mounts: 1 Type:  DevInfo: 0x0 Attributes: 0x0
        PathComponentMax: 0 Status: 0 type: 0 Serial Number: 0x0

        1) \\192.168.1.1\Music Mounts: 1 Type: NTFS DevInfo: 0x0 Attributes: 0x2f
        PathComponentMax: 255 Status: 0 type: 0 Serial Number: 0x0 POSIX Extensions


        MIDs: 
--

Witness registrations:

findmnt --verify --verbose

/mnt/Music
   [ ] target exists
   [ ] VFS options: ro
   [ ] FS options: vers=1.0,username=guest,password=guest,iocharset=utf8,sec=ntlmv2
   [ ] userspace options: users,noauto
   [ ] do not check //192.168.1.1/Music source (pseudo/net)
   [ ] do not check //192.168.1.1/Music FS type (pseudo/net)

Last edited by aocab (2022-12-30 05:33:20)

Offline

#2 2022-12-27 23:11:59

aocab
Member
Registered: 2013-08-15
Posts: 33

Re: [solved] system crash accessing cifs 1.0 shares

Made another attempt at installing the LTS kernel.
No system crash when accessing cifs 1.0 shares.
Playing music now.

Now to figure out why it's not working in kernel 6.

Offline

#3 2022-12-28 00:04:26

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,788

Re: [solved] system crash accessing cifs 1.0 shares

I would say this is probably expected. 1.0 is long, long, LONG obsolete, and many components for it are being removed from the kernel.

Last edited by Scimmia (2022-12-28 00:11:36)

Offline

#4 2022-12-28 07:54:47

d.ALT
Member
Registered: 2019-05-10
Posts: 943

Re: [solved] system crash accessing cifs 1.0 shares

Scimmia wrote:

1.0 is long, long, LONG obsolete

^This

Any particular reason on using 1.0?


<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#5 2022-12-28 23:09:07

aocab
Member
Registered: 2013-08-15
Posts: 33

Re: [solved] system crash accessing cifs 1.0 shares

d.ALT wrote:
Scimmia wrote:

1.0 is long, long, LONG obsolete

^This

Any particular reason on using 1.0?

It's what the old router (linksys ea6350) supports. That plus ftp and dlna.
I can still access the files using a browser to access the twonky dlna server. And vlc has a built in dlna client.
I just found it easier to access the files using smb and audacious.

Offline

#6 2022-12-29 03:00:34

Toolybird
Member
Registered: 2017-09-30
Posts: 72

Re: [solved] system crash accessing cifs 1.0 shares

For reference, this issue was also reported to the bug tracker [1]

[1] https://bugs.archlinux.org/task/76939

Offline

#7 2022-12-29 09:03:20

seth
Member
Registered: 2012-09-03
Posts: 54,323

Re: [solved] system crash accessing cifs 1.0 shares

I just found it easier to access the files using smb and audacious.

https://wiki.archlinux.org/title/CurlFtpFS

----

Bisecting? No time to even build mainline or rc kernels from AUR/git, and no chaotic-aur repo yet exist for arch...
I'd guess anyone could easy replicate the issue with an WinXP (32-bit) share.

"I want to use the shitty protocol security-barndoor that graced us w/ wannacry, but I'm too busy debugging it, please someone else install WinXP!"
grrr…

And don't use SMB1 FFS!

"VFS: bogus file nlink value 0" is a stale file handle, the message is generic and perhaps even irrelevant.
"mount error(20): Not a directory" is more interesting and typically a permission/UID mapping issue.
The bug reporter could try "noposix", "nosetuids" and maybe "noserverinfo", though I'm not sure this is actually related to the crash ITT - certainly not if the OP doesn't get similar errors as well.

Online

#8 2022-12-29 15:41:08

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,998

Re: [solved] system crash accessing cifs 1.0 shares

Might I suggest a different tack here....

Your router is supported by DD-WRT. https://wiki.dd-wrt.com/wiki/index.php/Linksys_EA6300
With modern firmware, you can get SMB 2.x and 3.x, ftp, sftp, DLNA and VPNs.  And a SSH connection to the Linux running on the router (if you so choose) in addition to a web interface.  And you can have vlans.

And, it probably will alleviate other security holes in your existing router that have not been patched either.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#9 2022-12-29 18:53:40

aocab
Member
Registered: 2013-08-15
Posts: 33

Re: [solved] system crash accessing cifs 1.0 shares

ewaller wrote:

Might I suggest a different tack here....

Your router is supported by DD-WRT. https://wiki.dd-wrt.com/wiki/index.php/Linksys_EA6300

Thank you for pointing that out.
DD-WRT is now installed.

Last edited by aocab (2022-12-29 18:53:58)

Offline

#10 2022-12-29 21:54:55

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: [solved] system crash accessing cifs 1.0 shares

Please remember to mark the thread as [SOLVED].
CoC - How to post


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#11 2022-12-30 05:32:03

aocab
Member
Registered: 2013-08-15
Posts: 33

Re: [solved] system crash accessing cifs 1.0 shares

Used the information found here to get it working (sort of):
EA 6350 forum thread

The router will occasionally revert back to Linksys factory firmware after a reboot.
Major annoyance.

Last edited by aocab (2022-12-31 23:06:09)

Offline

#12 2023-01-30 02:44:25

aocab
Member
Registered: 2013-08-15
Posts: 33

Re: [solved] system crash accessing cifs 1.0 shares

Looks like the issue is resolved for me with kernel 6.1.8.

Offline

Board footer

Powered by FluxBB