* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review [not found] ` <20230509080658.GA152864@d6921c044a31> @ 2023-05-09 13:10 ` Rudi Heitbaum 2023-05-09 13:56 ` Greg Kroah-Hartman 0 siblings, 1 reply; 14+ messages in thread From: Rudi Heitbaum @ 2023-05-09 13:10 UTC (permalink / raw) To: Greg Kroah-Hartman Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 6.3.2 release. > > There are 694 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > Anything received after that time might be too late. > > Hi Greg, > > 6.3.2-rc2 tested. Hi Greg, Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. https://bugzilla.kernel.org/show_bug.cgi?id=217422 [ 9471.878611] BUG: kernel NULL pointer dereference, address: 0000000000000020 [ 9471.879864] #PF: supervisor read access in kernel mode [ 9471.881177] #PF: error_code(0x0000) - not-present page [ 9471.882447] PGD 0 P4D 0 [ 9471.883680] Oops: 0000 [#1] SMP NOPTI [ 9471.884932] CPU: 15 PID: 81926 Comm: .NET ThreadPool Tainted: P U O 6.3.2-rc2 #1 [ 9471.886494] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 [ 9471.887641] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] [ 9471.888795] Code: 00 00 00 49 89 c4 e8 d9 33 fe ff 85 c0 79 3a 48 63 d8 48 8b 3d 2b 61 6d cb 4c 89 e6 e8 83 b0 cc c1 48 81 fb 00 f0 ff ff 77 07 <48> 83 7b 20 00 74 41 4c 89 ee 48 89 df e8 e8 95 d1 c1 5b 41 5c 41 [ 9471.890042] RSP: 0018:ffff949ca06d7bb8 EFLAGS: 00010207 [ 9471.891291] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 000000000010e7c3 [ 9471.892555] RDX: 000000000010e7c2 RSI: ffffcb8fc0000000 RDI: 00000000000324f0 [ 9471.893824] RBP: ffff949ca06d7bd8 R08: ffff90e24896b000 R09: ffff90e24187e702 [ 9471.895081] R10: 0000000000000788 R11: 000000000000000a R12: ffff90e2c0caa000 [ 9471.896343] R13: ffff90e4fbf9e780 R14: ffff90e2dee4aeb8 R15: ffff90e2dee4af90 [ 9471.897615] FS: 00007f1f627fc6c0(0000) GS:ffff90e9779c0000(0000) knlGS:0000000000000000 [ 9471.898907] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 9471.900198] CR2: 0000000000000020 CR3: 000000015b37c001 CR4: 0000000000f70ea0 [ 9471.901503] PKRU: 55555554 [ 9471.902803] Call Trace: [ 9471.904099] <TASK> [ 9471.905381] __lookup_slow+0x81/0x130 [ 9471.906676] walk_component+0x10b/0x180 [ 9471.907966] path_lookupat+0x6a/0x1a0 [ 9471.909247] filename_lookup+0xd0/0x190 [ 9471.910533] ? schedule+0x59/0xa0 [ 9471.911813] ? futex_wait_queue+0x69/0xa0 [ 9471.913095] ? kmem_cache_alloc+0x47/0x3c0 [ 9471.914376] vfs_statx+0x84/0x150 [ 9471.915649] ? getname_flags+0x54/0x1d0 [ 9471.916926] vfs_fstatat+0x5c/0x80 [ 9471.918196] __do_sys_newlstat+0x37/0x70 [ 9471.919472] ? do_futex+0x12e/0x1a0 [ 9471.920758] ? __x64_sys_futex+0x112/0x1d0 [ 9471.922033] ? trace_hardirqs_off.part.0+0x20/0x70 [ 9471.923319] ? trace_hardirqs_on+0x2f/0x80 [ 9471.924598] __x64_sys_newlstat+0x1a/0x20 [ 9471.925897] do_syscall_64+0x3c/0x90 [ 9471.927639] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 9471.928951] RIP: 0033:0x7f206b4db184 [ 9471.930235] Code: 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 89 f8 48 89 f7 48 89 d6 83 f8 01 77 2b b8 06 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 04 c3 0f 1f 00 48 8b 15 61 cc 0b 00 f7 d8 64 [ 9471.931627] RSP: 002b:00007f1f627fa378 EFLAGS: 00000246 ORIG_RAX: 0000000000000006 [ 9471.933021] RAX: ffffffffffffffda RBX: 00007f1fbe6ad248 RCX: 00007f206b4db184 [ 9471.934435] RDX: 00007f1f627fa380 RSI: 00007f1f627fa380 RDI: 00007f1f627fa4f0 [ 9471.935850] RBP: 00007f1f627fa4d0 R08: 00007f1f627fa600 R09: 000000000000002e [ 9471.937263] R10: 00007f1ff1ba15e8 R11: 0000000000000246 R12: 00007f1fbc018408 [ 9471.938683] R13: 00007f1f627fa4f0 R14: 00007f1fbe6ad248 R15: 000000000000002e [ 9471.940106] </TASK> [ 9471.941523] Modules linked in: rfcomm veth 8021q xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype iptable_filter ip_tables x_tables br_netfilter bridge stp llc overlay ntfs3 exfat bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic ecc iwlmvm mac80211 libarc4 snd_hda_codec_hdmi iwlwifi wl(PO) snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel mei_pxp mei_hdcp x86_pkg_temp_thermal snd_hda_codec cfg80211 intel_powerclamp snd_hwdep intel_rapl_msr tpm_tis mei_me snd_hda_core idma64 tpm_tis_core intel_rapl_common mei snd_intel_dspcfg rfkill tpm_crb tpm rng_core pkcs8_key_parser fuse dmi_sysfs [ 9471.948020] CR2: 0000000000000020 [ 9471.949674] ---[ end trace 0000000000000000 ]--- [ 9471.949674] BUG: kernel NULL pointer dereference, address: 0000000000000020 [ 9471.951352] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] [ 9471.953035] #PF: supervisor read access in kernel mode [ 9471.954720] Code: 00 00 00 49 89 c4 e8 d9 33 fe ff 85 c0 79 3a 48 63 d8 48 8b 3d 2b 61 6d cb 4c 89 e6 e8 83 b0 cc c1 48 81 fb 00 f0 ff ff 77 07 <48> 83 7b 20 00 74 41 4c 89 ee 48 89 df e8 e8 95 d1 c1 5b 41 5c 41 [ 9471.956410] #PF: error_code(0x0000) - not-present page [ 9471.958201] RSP: 0018:ffff949ca06d7bb8 EFLAGS: 00010207 [ 9471.959982] PGD 0 P4D 0 [ 9471.961783] [ 9471.961783] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 000000000010e7c3 [ 9471.963554] [ 9471.965305] RDX: 000000000010e7c2 RSI: ffffcb8fc0000000 RDI: 00000000000324f0 [ 9471.967092] Oops: 0000 [#2] SMP NOPTI [ 9471.969251] RBP: ffff949ca06d7bd8 R08: ffff90e24896b000 R09: ffff90e24187e702 [ 9471.971054] CPU: 13 PID: 81947 Comm: .NET ThreadPool Tainted: P UD O 6.3.2-rc2 #1 [ 9471.972824] R10: 0000000000000788 R11: 000000000000000a R12: ffff90e2c0caa000 [ 9471.974610] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 [ 9471.976406] R13: ffff90e4fbf9e780 R14: ffff90e2dee4aeb8 R15: ffff90e2dee4af90 [ 9471.978206] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] [ 9471.980039] FS: 00007f1f627fc6c0(0000) GS:ffff90e9779c0000(0000) knlGS:0000000000000000 [ 9471.981887] Code: 00 00 00 49 89 c4 e8 d9 33 fe ff 85 c0 79 3a 48 63 d8 48 8b 3d 2b 61 6d cb 4c 89 e6 e8 83 b0 cc c1 48 81 fb 00 f0 ff ff 77 07 <48> 83 7b 20 00 74 41 4c 89 ee 48 89 df e8 e8 95 d1 c1 5b 41 5c 41 [ 9471.983737] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 9471.985576] RSP: 0018:ffff949c8ff7fbb8 EFLAGS: 00010207 [ 9471.987490] CR2: 0000000000000020 CR3: 000000015b37c001 CR4: 0000000000f70ea0 [ 9471.989339] [ 9471.991159] PKRU: 55555554 [ 9471.991160] note: .NET ThreadPool[81926] exited with irqs disabled [ 9471.992978] RAX: ffff90e24ac6d001 RBX: 0000000000000000 RCX: 00000000000eea5f [ 9472.000239] RDX: 00000000000eea5e RSI: ffffcb8fc0000000 RDI: 00000000000324f0 [ 9472.002036] RBP: ffff949c8ff7fbd8 R08: ffff90e24ac69002 R09: ffff90e3b570a5ea [ 9472.003843] R10: ffff90e25c340000 R11: 000000000000000a R12: ffff90e24ac69000 [ 9472.005628] R13: ffff90e4fbeb2fc0 R14: ffff90e2dee4e488 R15: ffff90e2dee4e560 [ 9472.007414] FS: 00007f1f01ffb6c0(0000) GS:ffff90e977940000(0000) knlGS:0000000000000000 [ 9472.009218] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 9472.011496] CR2: 0000000000000020 CR3: 000000015b37c006 CR4: 0000000000f70ea0 [ 9472.013344] PKRU: 55555554 [ 9472.015171] Call Trace: [ 9472.016999] <TASK> [ 9472.018813] __lookup_slow+0x81/0x130 [ 9472.020639] walk_component+0x10b/0x180 [ 9472.022454] path_lookupat+0x6a/0x1a0 [ 9472.024289] filename_lookup+0xd0/0x190 [ 9472.026106] ? sched_clock+0xd/0x20 [ 9472.027930] ? sched_clock_cpu+0x14/0x190 [ 9472.029753] ? __smp_call_single_queue+0x40/0x50 [ 9472.031576] ? ttwu_queue_wakelist+0xfd/0x100 [ 9472.033403] ? kmem_cache_alloc+0x47/0x3c0 [ 9472.035232] vfs_statx+0x84/0x150 [ 9472.037056] ? getname_flags+0x54/0x1d0 [ 9472.038876] vfs_fstatat+0x5c/0x80 [ 9472.040699] __do_sys_newlstat+0x37/0x70 [ 9472.042515] ? do_futex+0x12e/0x1a0 [ 9472.044332] ? __x64_sys_futex+0x112/0x1d0 [ 9472.046146] ? switch_fpu_return+0x55/0xd0 [ 9472.047912] ? trace_hardirqs_off.part.0+0x20/0x70 [ 9472.049636] ? trace_hardirqs_on+0x2f/0x80 [ 9472.051409] __x64_sys_newlstat+0x1a/0x20 [ 9472.053491] do_syscall_64+0x3c/0x90 [ 9472.055213] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 9472.056940] RIP: 0033:0x7f206b4db184 [ 9472.058658] Code: 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 89 f8 48 89 f7 48 89 d6 83 f8 01 77 2b b8 06 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 04 c3 0f 1f 00 48 8b 15 61 cc 0b 00 f7 d8 64 [ 9472.060473] RSP: 002b:00007f1f01ff9378 EFLAGS: 00000246 ORIG_RAX: 0000000000000006 [ 9472.062212] RAX: ffffffffffffffda RBX: 00007f1fbe689478 RCX: 00007f206b4db184 [ 9472.063898] RDX: 00007f1f01ff9380 RSI: 00007f1f01ff9380 RDI: 00007f1f01ff94f0 [ 9472.065522] RBP: 00007f1f01ff94d0 R08: 00007f1f01ff9600 R09: 0000000000000035 [ 9472.067094] R10: 00007f1ff1ba15e8 R11: 0000000000000246 R12: 00007f1fbc018408 [ 9472.068665] R13: 00007f1f01ff94f0 R14: 00007f1fbe689478 R15: 0000000000000035 [ 9472.070238] </TASK> [ 9472.071799] Modules linked in: rfcomm veth 8021q xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype iptable_filter ip_tables x_tables br_netfilter bridge stp llc overlay ntfs3 exfat bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic ecc iwlmvm mac80211 libarc4 snd_hda_codec_hdmi iwlwifi wl(PO) snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel mei_pxp mei_hdcp x86_pkg_temp_thermal snd_hda_codec cfg80211 intel_powerclamp snd_hwdep intel_rapl_msr tpm_tis mei_me snd_hda_core idma64 tpm_tis_core intel_rapl_common mei snd_intel_dspcfg rfkill tpm_crb tpm rng_core pkcs8_key_parser fuse dmi_sysfs [ 9472.078669] CR2: 0000000000000020 [ 9472.080365] ---[ end trace 0000000000000000 ]--- ... [ 9476.855987] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] [ 9476.857799] Code: 00 00 00 49 89 c4 e8 d9 33 fe ff 85 c0 79 3a 48 63 d8 48 8b 3d 2b 61 6d cb 4c 89 e6 e8 83 b0 cc c1 48 81 fb 00 f0 ff ff 77 07 <48> 83 7b 20 00 74 41 4c 89 ee 48 89 df e8 e8 95 d1 c1 5b 41 5c 41 [ 9476.859687] RSP: 0018:ffff949ca06d7bb8 EFLAGS: 00010207 [ 9476.861557] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 000000000010e7c3 [ 9476.863433] RDX: 000000000010e7c2 RSI: ffffcb8fc0000000 RDI: 00000000000324f0 [ 9476.865302] RBP: ffff949ca06d7bd8 R08: ffff90e24896b000 R09: ffff90e24187e702 [ 9476.867160] R10: 0000000000000788 R11: 000000000000000a R12: ffff90e2c0caa000 [ 9476.869017] R13: ffff90e4fbf9e780 R14: ffff90e2dee4aeb8 R15: ffff90e2dee4af90 [ 9476.870864] FS: 00007f1f617fa6c0(0000) GS:ffff90e977900000(0000) knlGS:0000000000000000 [ 9476.872702] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 9476.874529] CR2: 0000000000000020 CR3: 000000015b37c003 CR4: 0000000000f70ea0 [ 9476.876353] PKRU: 55555554 [ 9476.878161] note: .NET ThreadPool[81927] exited with irqs disabled -- Rudi ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-09 13:10 ` [PATCH 6.3 000/694] 6.3.2-rc2 review Rudi Heitbaum @ 2023-05-09 13:56 ` Greg Kroah-Hartman 2023-05-09 14:58 ` Rudi Heitbaum 0 siblings, 1 reply; 14+ messages in thread From: Greg Kroah-Hartman @ 2023-05-09 13:56 UTC (permalink / raw) To: Rudi Heitbaum Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 6.3.2 release. > > > There are 694 patches in this series, all will be posted as a response > > > to this one. If anyone has any issues with these being applied, please > > > let me know. > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > Anything received after that time might be too late. > > > > Hi Greg, > > > > 6.3.2-rc2 tested. > > Hi Greg, > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. Can you reproduce this without the extern, gpl-violation module loaded? thanks, greg k-h ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-09 13:56 ` Greg Kroah-Hartman @ 2023-05-09 14:58 ` Rudi Heitbaum 2023-05-09 19:30 ` Naresh Kamboju 2023-05-10 7:25 ` Greg Kroah-Hartman 0 siblings, 2 replies; 14+ messages in thread From: Rudi Heitbaum @ 2023-05-09 14:58 UTC (permalink / raw) To: Greg Kroah-Hartman Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > There are 694 patches in this series, all will be posted as a response > > > > to this one. If anyone has any issues with these being applied, please > > > > let me know. > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > Anything received after that time might be too late. > > > > > > Hi Greg, > > > > > > 6.3.2-rc2 tested. > > > > Hi Greg, > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > Can you reproduce this without the extern, gpl-violation module loaded? > > thanks, > > greg k-h Hi Greg, I dropped the bcm_sta and recompiled and commented out the i915.guc=3 and was able to reproduce. [ 84.745080] BUG: kernel NULL pointer dereference, address: 0000000000000020 [ 84.746239] #PF: supervisor read access in kernel mode [ 84.747599] #PF: error_code(0x0000) - not-present page [ 84.748929] PGD 0 P4D 0 [ 84.750240] Oops: 0000 [#1] SMP NOPTI [ 84.751575] CPU: 2 PID: 3176 Comm: .NET ThreadPool Not tainted 6.3.2-rc2 #1 [ 84.752998] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 [ 84.754474] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] [ 84.755899] Code: 00 00 00 49 89 c4 e8 d9 33 fe ff 85 c0 79 3a 48 63 d8 48 8b 3d 2b 51 74 e4 4c 89 e6 e8 83 a0 d3 da 48 81 fb 00 f0 ff ff 77 07 <48> 83 7b 20 00 74 41 4c 89 ee 48 89 df e8 e8 85 d8 da 5b 41 5c 41 [ 84.757430] RSP: 0018:ffff9dea4072bbb8 EFLAGS: 00010207 [ 84.758943] RAX: ffff94fcf4efb001 RBX: 0000000000000000 RCX: 0000000000058509 [ 84.760485] RDX: 0000000000058508 RSI: ffffc40100000000 RDI: 00000000000324f0 [ 84.762031] RBP: ffff9dea4072bbd8 R08: ffff94fcf4eff008 R09: ffff94fcaaeb2c88 [ 84.763621] R10: ffff94fc58fc0000 R11: 0000000000000013 R12: ffff94fcf4eff000 [ 84.765191] R13: ffff94fcfe67a600 R14: ffff94fcdf008470 R15: ffff94fcdf008548 [ 84.766773] FS: 00007f51d1ffb6c0(0000) GS:ffff950377680000(0000) knlGS:0000000000000000 [ 84.768386] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 84.770001] CR2: 0000000000000020 CR3: 0000000177b5a004 CR4: 0000000000f70ea0 [ 84.771632] PKRU: 55555554 [ 84.773261] Call Trace: [ 84.774890] <TASK> [ 84.776499] __lookup_slow+0x81/0x130 [ 84.778107] walk_component+0x10b/0x180 [ 84.779719] path_lookupat+0x6a/0x1a0 [ 84.781368] filename_lookup+0xd0/0x190 [ 84.782978] ? sched_clock+0xd/0x20 [ 84.784592] ? sched_clock_cpu+0x14/0x190 [ 84.786202] ? __smp_call_single_queue+0x40/0x50 [ 84.787816] ? ttwu_queue_wakelist+0xfd/0x100 [ 84.789436] ? kmem_cache_alloc+0x47/0x3c0 [ 84.791050] vfs_statx+0x84/0x150 [ 84.792669] ? getname_flags+0x54/0x1d0 [ 84.794288] vfs_fstatat+0x5c/0x80 [ 84.795905] __do_sys_newlstat+0x37/0x70 [ 84.797549] ? do_futex+0x12e/0x1a0 [ 84.799166] ? __x64_sys_futex+0x112/0x1d0 [ 84.800773] ? trace_hardirqs_off.part.0+0x20/0x70 [ 84.802395] ? trace_hardirqs_on+0x2f/0x80 [ 84.803998] __x64_sys_newlstat+0x1a/0x20 [ 84.805599] do_syscall_64+0x3c/0x90 [ 84.807193] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 84.808802] RIP: 0033:0x7f529d04e184 [ 84.810409] Code: 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 89 f8 48 89 f7 48 89 d6 83 f8 01 77 2b b8 06 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 04 c3 0f 1f 00 48 8b 15 61 cc 0b 00 f7 d8 64 [ 84.812161] RSP: 002b:00007f51d1ff9028 EFLAGS: 00000246 ORIG_RAX: 0000000000000006 [ 84.813959] RAX: ffffffffffffffda RBX: 00007f51eee2c010 RCX: 00007f529d04e184 [ 84.815723] RDX: 00007f51d1ff9030 RSI: 00007f51d1ff9030 RDI: 00007f51d1ff91a0 [ 84.817496] RBP: 00007f51d1ff9180 R08: 00007f51d1ff92b0 R09: 0000000000000029 [ 84.819271] R10: 00007f52237915e8 R11: 0000000000000246 R12: 00007f51ec018408 [ 84.821051] R13: 00007f51d1ff91a0 R14: 00007f51eee2c010 R15: 0000000000000029 [ 84.822845] </TASK> [ 84.824621] Modules linked in: rfcomm xt_nat xt_tcpudp veth 8021q xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype iptable_filter ip_tables x_tables br_netfilter bridge stp llc overlay ntfs3 bnep btusb btrtl btbcm btintel btmtk bluetooth exfat ecdh_generic ecc iwlmvm snd_hda_codec_hdmi mac80211 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio libarc4 iwlwifi snd_hda_intel snd_hda_codec cfg80211 mei_pxp snd_hwdep mei_hdcp intel_rapl_msr x86_pkg_temp_thermal intel_powerclamp snd_hda_core intel_rapl_common mei_me snd_intel_dspcfg tpm_tis tpm_tis_core idma64 mei rfkill tpm_crb tpm rng_core pkcs8_key_parser fuse dmi_sysfs [ 84.830844] CR2: 0000000000000020 [ 84.832982] ---[ end trace 0000000000000000 ]--- ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-09 14:58 ` Rudi Heitbaum @ 2023-05-09 19:30 ` Naresh Kamboju 2023-05-10 6:53 ` Rudi Heitbaum 2023-05-10 7:25 ` Greg Kroah-Hartman 1 sibling, 1 reply; 14+ messages in thread From: Naresh Kamboju @ 2023-05-09 19:30 UTC (permalink / raw) To: Rudi Heitbaum Cc: Greg Kroah-Hartman, stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Tue, 9 May 2023 at 20:28, Rudi Heitbaum <rudi@heitbaum.com> wrote: > > On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > > There are 694 patches in this series, all will be posted as a response > > > > > to this one. If anyone has any issues with these being applied, please > > > > > let me know. > > > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > > Anything received after that time might be too late. > > > > > > > > Hi Greg, > > > > > > > > 6.3.2-rc2 tested. > > > > > > Hi Greg, > > > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > > > Can you reproduce this without the extern, gpl-violation module loaded? Please share the steps to reproduce test case / Kconfigs / device under test environment / firmware / boot loaders. - Naresh ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-09 19:30 ` Naresh Kamboju @ 2023-05-10 6:53 ` Rudi Heitbaum 0 siblings, 0 replies; 14+ messages in thread From: Rudi Heitbaum @ 2023-05-10 6:53 UTC (permalink / raw) To: Naresh Kamboju Cc: Greg Kroah-Hartman, stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Wed, 10 May 2023 at 05:30, Naresh Kamboju <naresh.kamboju@linaro.org> wrote: > > On Tue, 9 May 2023 at 20:28, Rudi Heitbaum <rudi@heitbaum.com> wrote: > > > > On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > > > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > > > There are 694 patches in this series, all will be posted as a response > > > > > > to this one. If anyone has any issues with these being applied, please > > > > > > let me know. > > > > > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > > > Anything received after that time might be too late. > > > > > > > > > > Hi Greg, > > > > > > > > > > 6.3.2-rc2 tested. > > > > > > > > Hi Greg, > > > > > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > > > > > Can you reproduce this without the extern, gpl-violation module loaded? > > Please share the steps to reproduce > test case / Kconfigs / device under test environment / firmware / boot loaders. Hi Naresh, Test case: - general use - no specific case Test device: LibreELEC with docker used as media player with docker for development / package testing for LibreELEC [ 0.000000] microcode: updated early: 0x421 -> 0x429, date = 2023-01-11 [ 0.000000] DMI: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 ntfs3 volume is: /dev/sdb2 on /var/media/L-Z type ntfs3 (rw,relatime,uid=0,gid=0,fmask=0133,iocharset=utf8) *-usb:1 description: Mass storage device product: USB to ATA/ATAPI Bridge vendor: JMicron physical id: 2 bus info: usb@4:2.2 logical name: scsi1 version: 5.08 serial: capabilities: usb-3.00 scsi configuration: driver=uas maxpower=896mA speed=5000Mbit/s *-disk description: SCSI Disk product: Generic vendor: JMicron physical id: 0.0.0 bus info: scsi@1:0.0.0 logical name: /dev/sdb version: 0508 serial: size: 10TiB (12TB) capabilities: gpt-1.00 partitioned partitioned:gpt configuration: ansiversion=6 guid=7fe84503-eeb0-4ee6-806d-9cbe22dc50f2 logicalsectorsize=512 sectorsize=4096 *-volume:0 description: reserved partition vendor: Windows physical id: 1 bus info: scsi@1:0.0.0,1 logical name: /dev/sdb1 serial: capacity: 15MiB capabilities: nofs configuration: name=Microsoft reserved partition *-volume:1 description: Windows NTFS volume vendor: Windows physical id: 2 bus info: scsi@1:0.0.0,2 logical name: /dev/sdb2 logical name: /var/media/L-Z version: 3.1 serial: size: 935GiB capacity: 10TiB capabilities: ntfs initialized configuration: clustersize=4096 created=2022-10-01 10:18:29 filesystem=ntfs label=L-Z mount.fstype=ntfs3 mount.options=rw,relatime,uid=0,gid=0,fmask=0133,iocharset=utf8 name=Basic data partition state=mounted Operating system: - LibreELEC - https://libreelec.tv/ (master+ branch) Boot loader: - syslinux Kconfig: - https://github.com/LibreELEC/LibreELEC.tv/blob/master/projects/Generic/linux/linux.x86_64.conf > - Naresh ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-09 14:58 ` Rudi Heitbaum 2023-05-09 19:30 ` Naresh Kamboju @ 2023-05-10 7:25 ` Greg Kroah-Hartman 2023-05-10 8:29 ` Rudi Heitbaum 1 sibling, 1 reply; 14+ messages in thread From: Greg Kroah-Hartman @ 2023-05-10 7:25 UTC (permalink / raw) To: Rudi Heitbaum Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Tue, May 09, 2023 at 02:58:06PM +0000, Rudi Heitbaum wrote: > On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > > There are 694 patches in this series, all will be posted as a response > > > > > to this one. If anyone has any issues with these being applied, please > > > > > let me know. > > > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > > Anything received after that time might be too late. > > > > > > > > Hi Greg, > > > > > > > > 6.3.2-rc2 tested. > > > > > > Hi Greg, > > > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > > > Can you reproduce this without the extern, gpl-violation module loaded? > > > > thanks, > > > > greg k-h > > Hi Greg, > > I dropped the bcm_sta and recompiled and commented out the i915.guc=3 > and was able to reproduce. > > [ 84.745080] BUG: kernel NULL pointer dereference, address: 0000000000000020 > [ 84.746239] #PF: supervisor read access in kernel mode > [ 84.747599] #PF: error_code(0x0000) - not-present page > [ 84.748929] PGD 0 P4D 0 > [ 84.750240] Oops: 0000 [#1] SMP NOPTI > [ 84.751575] CPU: 2 PID: 3176 Comm: .NET ThreadPool Not tainted 6.3.2-rc2 #1 > [ 84.752998] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > [ 84.754474] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] And do you get this same crash on ntfs3 on 6.4-rc1? Is this a new regression, or does it also show up on 6.3.1? And ntfs, ick, why? And .NET? What a combination... thanks, greg k-h ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-10 7:25 ` Greg Kroah-Hartman @ 2023-05-10 8:29 ` Rudi Heitbaum 2023-05-10 9:09 ` Greg Kroah-Hartman 0 siblings, 1 reply; 14+ messages in thread From: Rudi Heitbaum @ 2023-05-10 8:29 UTC (permalink / raw) To: Greg Kroah-Hartman Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Wed, 10 May 2023 at 17:25, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > > On Tue, May 09, 2023 at 02:58:06PM +0000, Rudi Heitbaum wrote: > > On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > > > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > > > There are 694 patches in this series, all will be posted as a response > > > > > > to this one. If anyone has any issues with these being applied, please > > > > > > let me know. > > > > > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > > > Anything received after that time might be too late. > > > > > > > > > > Hi Greg, > > > > > > > > > > 6.3.2-rc2 tested. > > > > > > > > Hi Greg, > > > > > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > > > > > Can you reproduce this without the extern, gpl-violation module loaded? > > > > > > thanks, > > > > > > greg k-h > > > > Hi Greg, > > > > I dropped the bcm_sta and recompiled and commented out the i915.guc=3 > > and was able to reproduce. > > > > [ 84.745080] BUG: kernel NULL pointer dereference, address: 0000000000000020 > > [ 84.746239] #PF: supervisor read access in kernel mode > > [ 84.747599] #PF: error_code(0x0000) - not-present page > > [ 84.748929] PGD 0 P4D 0 > > [ 84.750240] Oops: 0000 [#1] SMP NOPTI > > [ 84.751575] CPU: 2 PID: 3176 Comm: .NET ThreadPool Not tainted 6.3.2-rc2 #1 > > [ 84.752998] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > > [ 84.754474] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] > > And do you get this same crash on ntfs3 on 6.4-rc1? Is this a new > regression, or does it also show up on 6.3.1? Tested with 6.3.1 during the day today. No errors, and had been running 6.3.1 with no issue. Retested with 6.3.2-rc2 and problem immediately evident. So yes - I believe a regression. I have built and am now testing 6.4.0-rc1 this evening - no errors so far. [ 0.000000] Linux version 6.4.0-rc1 (docker@1ccd349e2545) (x86_64-libreelec-linux-gnu-gcc-13.1.0 (GCC) 13.1.0, GNU ld (GNU Binutils) 2.40) #1 SMP Wed May 10 07:51:37 UTC 2023 > And ntfs, ick, why? And .NET? What a combination... Joys of media players. Test device gets to test exfat, ntfs3, .NET, and throw in a compile host/GHA runner to put it through paces. > thanks, > > greg k-h ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-10 8:29 ` Rudi Heitbaum @ 2023-05-10 9:09 ` Greg Kroah-Hartman 2023-05-10 11:58 ` Rudi Heitbaum 0 siblings, 1 reply; 14+ messages in thread From: Greg Kroah-Hartman @ 2023-05-10 9:09 UTC (permalink / raw) To: Rudi Heitbaum Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Wed, May 10, 2023 at 06:29:23PM +1000, Rudi Heitbaum wrote: > On Wed, 10 May 2023 at 17:25, Greg Kroah-Hartman > <gregkh@linuxfoundation.org> wrote: > > > > On Tue, May 09, 2023 at 02:58:06PM +0000, Rudi Heitbaum wrote: > > > On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > > > > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > > > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > > > > There are 694 patches in this series, all will be posted as a response > > > > > > > to this one. If anyone has any issues with these being applied, please > > > > > > > let me know. > > > > > > > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > > > > Anything received after that time might be too late. > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > 6.3.2-rc2 tested. > > > > > > > > > > Hi Greg, > > > > > > > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > > > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > > > > > > > Can you reproduce this without the extern, gpl-violation module loaded? > > > > > > > > thanks, > > > > > > > > greg k-h > > > > > > Hi Greg, > > > > > > I dropped the bcm_sta and recompiled and commented out the i915.guc=3 > > > and was able to reproduce. > > > > > > [ 84.745080] BUG: kernel NULL pointer dereference, address: 0000000000000020 > > > [ 84.746239] #PF: supervisor read access in kernel mode > > > [ 84.747599] #PF: error_code(0x0000) - not-present page > > > [ 84.748929] PGD 0 P4D 0 > > > [ 84.750240] Oops: 0000 [#1] SMP NOPTI > > > [ 84.751575] CPU: 2 PID: 3176 Comm: .NET ThreadPool Not tainted 6.3.2-rc2 #1 > > > [ 84.752998] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > > > [ 84.754474] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] > > > > And do you get this same crash on ntfs3 on 6.4-rc1? Is this a new > > regression, or does it also show up on 6.3.1? > > Tested with 6.3.1 during the day today. No errors, and had been > running 6.3.1 with no issue. Retested with 6.3.2-rc2 and problem > immediately evident. So yes - I believe a regression. > > I have built and am now testing 6.4.0-rc1 this evening - no errors so far. > > [ 0.000000] Linux version 6.4.0-rc1 (docker@1ccd349e2545) > (x86_64-libreelec-linux-gnu-gcc-13.1.0 (GCC) 13.1.0, GNU ld (GNU > Binutils) 2.40) #1 SMP Wed May 10 07:51:37 UTC 2023 > > > And ntfs, ick, why? And .NET? What a combination... > > Joys of media players. Test device gets to test exfat, ntfs3, .NET, > and throw in a compile host/GHA runner to put it through paces. Yeah, this should work. Thanks for verifying this works on other releases. Any chance you can do 'git bisect' to track down the offending commit? In looking things over, I don't see anything obvious... thanks, greg k-h ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-10 9:09 ` Greg Kroah-Hartman @ 2023-05-10 11:58 ` Rudi Heitbaum 2023-05-10 23:00 ` Greg Kroah-Hartman 0 siblings, 1 reply; 14+ messages in thread From: Rudi Heitbaum @ 2023-05-10 11:58 UTC (permalink / raw) To: Greg Kroah-Hartman Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Wed, 10 May 2023 at 19:09, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > > On Wed, May 10, 2023 at 06:29:23PM +1000, Rudi Heitbaum wrote: > > On Wed, 10 May 2023 at 17:25, Greg Kroah-Hartman > > <gregkh@linuxfoundation.org> wrote: > > > > > > On Tue, May 09, 2023 at 02:58:06PM +0000, Rudi Heitbaum wrote: > > > > On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > > > > > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > > > > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > > > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > > > > > There are 694 patches in this series, all will be posted as a response > > > > > > > > to this one. If anyone has any issues with these being applied, please > > > > > > > > let me know. > > > > > > > > > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > > > > > Anything received after that time might be too late. > > > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > > > 6.3.2-rc2 tested. > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > > > > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > > > > > > > > > Can you reproduce this without the extern, gpl-violation module loaded? > > > > > > > > > > thanks, > > > > > > > > > > greg k-h > > > > > > > > Hi Greg, > > > > > > > > I dropped the bcm_sta and recompiled and commented out the i915.guc=3 > > > > and was able to reproduce. > > > > > > > > [ 84.745080] BUG: kernel NULL pointer dereference, address: 0000000000000020 > > > > [ 84.746239] #PF: supervisor read access in kernel mode > > > > [ 84.747599] #PF: error_code(0x0000) - not-present page > > > > [ 84.748929] PGD 0 P4D 0 > > > > [ 84.750240] Oops: 0000 [#1] SMP NOPTI > > > > [ 84.751575] CPU: 2 PID: 3176 Comm: .NET ThreadPool Not tainted 6.3.2-rc2 #1 > > > > [ 84.752998] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > > > > [ 84.754474] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] > > > > > > And do you get this same crash on ntfs3 on 6.4-rc1? Is this a new > > > regression, or does it also show up on 6.3.1? > > > > Tested with 6.3.1 during the day today. No errors, and had been > > running 6.3.1 with no issue. Retested with 6.3.2-rc2 and problem > > immediately evident. So yes - I believe a regression. > > > > I have built and am now testing 6.4.0-rc1 this evening - no errors so far. > > > > [ 0.000000] Linux version 6.4.0-rc1 (docker@1ccd349e2545) > > (x86_64-libreelec-linux-gnu-gcc-13.1.0 (GCC) 13.1.0, GNU ld (GNU > > Binutils) 2.40) #1 SMP Wed May 10 07:51:37 UTC 2023 > > > > > And ntfs, ick, why? And .NET? What a combination... > > > > Joys of media players. Test device gets to test exfat, ntfs3, .NET, > > and throw in a compile host/GHA runner to put it through paces. > > Yeah, this should work. Thanks for verifying this works on other > releases. Any chance you can do 'git bisect' to track down the > offending commit? In looking things over, I don't see anything > obvious... Hi Greg, I can confirm the offending commit in 6.3.2-rc2 is bf11fd528a97 fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup() Regards Rudi > thanks, > > greg k-h ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-10 11:58 ` Rudi Heitbaum @ 2023-05-10 23:00 ` Greg Kroah-Hartman 2023-05-11 8:30 ` Rudi Heitbaum 0 siblings, 1 reply; 14+ messages in thread From: Greg Kroah-Hartman @ 2023-05-10 23:00 UTC (permalink / raw) To: Rudi Heitbaum Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Wed, May 10, 2023 at 09:58:06PM +1000, Rudi Heitbaum wrote: > On Wed, 10 May 2023 at 19:09, Greg Kroah-Hartman > <gregkh@linuxfoundation.org> wrote: > > > > On Wed, May 10, 2023 at 06:29:23PM +1000, Rudi Heitbaum wrote: > > > On Wed, 10 May 2023 at 17:25, Greg Kroah-Hartman > > > <gregkh@linuxfoundation.org> wrote: > > > > > > > > On Tue, May 09, 2023 at 02:58:06PM +0000, Rudi Heitbaum wrote: > > > > > On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > > > > > > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > > > > > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > > > > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > > > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > > > > > > There are 694 patches in this series, all will be posted as a response > > > > > > > > > to this one. If anyone has any issues with these being applied, please > > > > > > > > > let me know. > > > > > > > > > > > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > > > > > > Anything received after that time might be too late. > > > > > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > > > > > 6.3.2-rc2 tested. > > > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > > > > > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > > > > > > > > > > > Can you reproduce this without the extern, gpl-violation module loaded? > > > > > > > > > > > > thanks, > > > > > > > > > > > > greg k-h > > > > > > > > > > Hi Greg, > > > > > > > > > > I dropped the bcm_sta and recompiled and commented out the i915.guc=3 > > > > > and was able to reproduce. > > > > > > > > > > [ 84.745080] BUG: kernel NULL pointer dereference, address: 0000000000000020 > > > > > [ 84.746239] #PF: supervisor read access in kernel mode > > > > > [ 84.747599] #PF: error_code(0x0000) - not-present page > > > > > [ 84.748929] PGD 0 P4D 0 > > > > > [ 84.750240] Oops: 0000 [#1] SMP NOPTI > > > > > [ 84.751575] CPU: 2 PID: 3176 Comm: .NET ThreadPool Not tainted 6.3.2-rc2 #1 > > > > > [ 84.752998] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > > > > > [ 84.754474] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] > > > > > > > > And do you get this same crash on ntfs3 on 6.4-rc1? Is this a new > > > > regression, or does it also show up on 6.3.1? > > > > > > Tested with 6.3.1 during the day today. No errors, and had been > > > running 6.3.1 with no issue. Retested with 6.3.2-rc2 and problem > > > immediately evident. So yes - I believe a regression. > > > > > > I have built and am now testing 6.4.0-rc1 this evening - no errors so far. > > > > > > [ 0.000000] Linux version 6.4.0-rc1 (docker@1ccd349e2545) > > > (x86_64-libreelec-linux-gnu-gcc-13.1.0 (GCC) 13.1.0, GNU ld (GNU > > > Binutils) 2.40) #1 SMP Wed May 10 07:51:37 UTC 2023 > > > > > > > And ntfs, ick, why? And .NET? What a combination... > > > > > > Joys of media players. Test device gets to test exfat, ntfs3, .NET, > > > and throw in a compile host/GHA runner to put it through paces. > > > > Yeah, this should work. Thanks for verifying this works on other > > releases. Any chance you can do 'git bisect' to track down the > > offending commit? In looking things over, I don't see anything > > obvious... > > Hi Greg, > > I can confirm the offending commit in 6.3.2-rc2 is > > bf11fd528a97 fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup() Thanks! Odd that this didn't show up for you on the other stable -rc releases, as that commit is also in those trees. I'll go revert this for now and ask the maintainer to send a fixed version. thanks, greg k-h ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-10 23:00 ` Greg Kroah-Hartman @ 2023-05-11 8:30 ` Rudi Heitbaum 2023-05-11 13:33 ` Greg Kroah-Hartman 2023-05-11 14:19 ` Linus Torvalds 0 siblings, 2 replies; 14+ messages in thread From: Rudi Heitbaum @ 2023-05-11 8:30 UTC (permalink / raw) To: Greg Kroah-Hartman Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Thu, 11 May 2023 at 09:00, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > > On Wed, May 10, 2023 at 09:58:06PM +1000, Rudi Heitbaum wrote: > > On Wed, 10 May 2023 at 19:09, Greg Kroah-Hartman > > <gregkh@linuxfoundation.org> wrote: > > > > > > On Wed, May 10, 2023 at 06:29:23PM +1000, Rudi Heitbaum wrote: > > > > On Wed, 10 May 2023 at 17:25, Greg Kroah-Hartman > > > > <gregkh@linuxfoundation.org> wrote: > > > > > > > > > > On Tue, May 09, 2023 at 02:58:06PM +0000, Rudi Heitbaum wrote: > > > > > > On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > > > > > > > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > > > > > > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > > > > > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > > > > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > > > > > > > There are 694 patches in this series, all will be posted as a response > > > > > > > > > > to this one. If anyone has any issues with these being applied, please > > > > > > > > > > let me know. > > > > > > > > > > > > > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > > > > > > > Anything received after that time might be too late. > > > > > > > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > > > > > > > 6.3.2-rc2 tested. > > > > > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > > > > > > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > > > > > > > > > > > > > Can you reproduce this without the extern, gpl-violation module loaded? > > > > > > > > > > > > > > thanks, > > > > > > > > > > > > > > greg k-h > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > I dropped the bcm_sta and recompiled and commented out the i915.guc=3 > > > > > > and was able to reproduce. > > > > > > > > > > > > [ 84.745080] BUG: kernel NULL pointer dereference, address: 0000000000000020 > > > > > > [ 84.746239] #PF: supervisor read access in kernel mode > > > > > > [ 84.747599] #PF: error_code(0x0000) - not-present page > > > > > > [ 84.748929] PGD 0 P4D 0 > > > > > > [ 84.750240] Oops: 0000 [#1] SMP NOPTI > > > > > > [ 84.751575] CPU: 2 PID: 3176 Comm: .NET ThreadPool Not tainted 6.3.2-rc2 #1 > > > > > > [ 84.752998] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > > > > > > [ 84.754474] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] > > > > > > > > > > And do you get this same crash on ntfs3 on 6.4-rc1? Is this a new > > > > > regression, or does it also show up on 6.3.1? > > > > > > > > Tested with 6.3.1 during the day today. No errors, and had been > > > > running 6.3.1 with no issue. Retested with 6.3.2-rc2 and problem > > > > immediately evident. So yes - I believe a regression. > > > > > > > > I have built and am now testing 6.4.0-rc1 this evening - no errors so far. > > > > > > > > [ 0.000000] Linux version 6.4.0-rc1 (docker@1ccd349e2545) > > > > (x86_64-libreelec-linux-gnu-gcc-13.1.0 (GCC) 13.1.0, GNU ld (GNU > > > > Binutils) 2.40) #1 SMP Wed May 10 07:51:37 UTC 2023 > > > > > > > > > And ntfs, ick, why? And .NET? What a combination... > > > > > > > > Joys of media players. Test device gets to test exfat, ntfs3, .NET, > > > > and throw in a compile host/GHA runner to put it through paces. > > > > > > Yeah, this should work. Thanks for verifying this works on other > > > releases. Any chance you can do 'git bisect' to track down the > > > offending commit? In looking things over, I don't see anything > > > obvious... > > > > Hi Greg, > > > > I can confirm the offending commit in 6.3.2-rc2 is > > > > bf11fd528a97 fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup() > > Thanks! Odd that this didn't show up for you on the other stable -rc > releases, as that commit is also in those trees. > > I'll go revert this for now and ask the maintainer to send a fixed > version. Hi Greg, I have run 6.1.28-rc2 today, and was able to trigger the error. So definitely bad in both 6.3 and 6.1. [13812.020209] BUG: kernel NULL pointer dereference, address: 0000000000000020 [13812.021322] #PF: supervisor read access in kernel mode [13812.022346] #PF: error_code(0x0000) - not-present page [13812.023591] PGD 0 P4D 0 [13812.024876] Oops: 0000 [#1] SMP NOPTI [13812.026088] CPU: 5 PID: 20386 Comm: .NET ThreadPool Not tainted 6.1.28-rc2 #1 [13812.027336] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 [13812.028593] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] [13812.029827] Code: 00 00 00 49 89 c4 e8 19 47 fe ff 85 c0 79 3a 48 63 d8 48 8b 3d 4b 1d 77 cd 4c 89 e6 e8 33 25 d1 c3 48 81 fb 00 f0 ff ff 77 07 <48> 83 7b 20 00 74 41 4c 89 ee 48 89 df e8 88 a5 d5 c3 5b 41 5c 41 [13812.031149] RSP: 0018:ffff91f40537bbc8 EFLAGS: 00010207 [13812.032408] RAX: ffff8a844946a001 RBX: 0000000000000000 RCX: 00000000000042f7 [13812.033650] RDX: 00000000000042f6 RSI: fffff40a00000000 RDI: 0000000000030ed0 [13812.034869] RBP: ffff91f40537bbe8 R08: ffff8a844946c01e R09: ffff8a8474d0387e [13812.036138] R10: ffff8a845a900000 R11: 0000000000000017 R12: ffff8a844946c000 [13812.037372] R13: ffff8a84db3fd2c0 R14: ffff8a84b44a0470 R15: ffff8a84b44a0548 [13812.039002] FS: 00007f437e7fc6c0(0000) GS:ffff8a8b77740000(0000) knlGS:0000000000000000 [13812.040509] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [13812.041741] CR2: 0000000000000020 CR3: 000000017835e006 CR4: 0000000000f70ea0 [13812.042986] PKRU: 55555554 [13812.044227] Call Trace: [13812.045464] <TASK> [13812.046708] __lookup_slow+0x81/0x130 [13812.047939] walk_component+0x10b/0x180 [13812.049169] path_lookupat+0x6a/0x1a0 [13812.050388] filename_lookup+0xd0/0x190 [13812.051612] vfs_statx+0x84/0x150 [13812.052838] ? getname_flags+0x54/0x1d0 [13812.054062] vfs_fstatat+0x5c/0x80 [13812.055284] __do_sys_newlstat+0x37/0x70 [13812.056580] ? trace_hardirqs_on+0x3a/0xe0 [13812.058429] __x64_sys_newlstat+0x1a/0x20 [13812.059878] do_syscall_64+0x3c/0x90 [13812.061109] entry_SYSCALL_64_after_hwframe+0x63/0xcd [13812.062369] RIP: 0033:0x7f447ea17184 [13812.063598] Code: 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 89 f8 48 89 f7 48 89 d6 83 f8 01 77 2b b8 06 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 04 c3 0f 1f 00 48 8b 15 61 cc 0b 00 f7 d8 64 [13812.064927] RSP: 002b:00007f437e7fa098 EFLAGS: 00000246 ORIG_RAX: 0000000000000006 [13812.066267] RAX: ffffffffffffffda RBX: 00007f43cf45a870 RCX: 00007f447ea17184 [13812.067601] RDX: 00007f437e7fa0a0 RSI: 00007f437e7fa0a0 RDI: 00007f437e7fa210 [13812.068940] RBP: 00007f437e7fa1f0 R08: 00007f437e7fa320 R09: 000000000000002d [13812.070276] R10: 00007f44051a15e8 R11: 0000000000000246 R12: 00007f43cc018408 [13812.071616] R13: 00007f437e7fa210 R14: 00007f43cf45a870 R15: 000000000000002d [13812.072960] </TASK> [13812.074295] Modules linked in: rfcomm xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype iptable_filter ip_tables x_tables br_netfilter bridge stp llc overlay 8021q ntfs3 bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic ecc exfat snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_hda_codec iwlwifi mei_hdcp snd_hwdep tpm_tis mei_pxp x86_pkg_temp_thermal snd_hda_core tpm_tis_core cfg80211 intel_rapl_msr mei_me intel_powerclamp snd_intel_dspcfg intel_rapl_common mei rfkill tpm_crb idma64 tpm rng_core pkcs8_key_parser fuse dmi_sysfs [13812.079600] CR2: 0000000000000020 [13812.081160] ---[ end trace 0000000000000000 ]--- > thanks, > > greg k-h ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-11 8:30 ` Rudi Heitbaum @ 2023-05-11 13:33 ` Greg Kroah-Hartman 2023-05-11 14:19 ` Linus Torvalds 1 sibling, 0 replies; 14+ messages in thread From: Greg Kroah-Hartman @ 2023-05-11 13:33 UTC (permalink / raw) To: Rudi Heitbaum Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Thu, May 11, 2023 at 06:30:02PM +1000, Rudi Heitbaum wrote: > On Thu, 11 May 2023 at 09:00, Greg Kroah-Hartman > <gregkh@linuxfoundation.org> wrote: > > > > On Wed, May 10, 2023 at 09:58:06PM +1000, Rudi Heitbaum wrote: > > > On Wed, 10 May 2023 at 19:09, Greg Kroah-Hartman > > > <gregkh@linuxfoundation.org> wrote: > > > > > > > > On Wed, May 10, 2023 at 06:29:23PM +1000, Rudi Heitbaum wrote: > > > > > On Wed, 10 May 2023 at 17:25, Greg Kroah-Hartman > > > > > <gregkh@linuxfoundation.org> wrote: > > > > > > > > > > > > On Tue, May 09, 2023 at 02:58:06PM +0000, Rudi Heitbaum wrote: > > > > > > > On Tue, May 09, 2023 at 03:56:42PM +0200, Greg Kroah-Hartman wrote: > > > > > > > > On Tue, May 09, 2023 at 01:10:32PM +0000, Rudi Heitbaum wrote: > > > > > > > > > On Tue, May 09, 2023 at 08:06:58AM +0000, Rudi Heitbaum wrote: > > > > > > > > > > On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote: > > > > > > > > > > > This is the start of the stable review cycle for the 6.3.2 release. > > > > > > > > > > > There are 694 patches in this series, all will be posted as a response > > > > > > > > > > > to this one. If anyone has any issues with these being applied, please > > > > > > > > > > > let me know. > > > > > > > > > > > > > > > > > > > > > > Responses should be made by Thu, 11 May 2023 03:05:05 +0000. > > > > > > > > > > > Anything received after that time might be too late. > > > > > > > > > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > > > > > > > > > 6.3.2-rc2 tested. > > > > > > > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > > > > > > > Further testing and have seen ntfs3: NULL pointer dereference with ntfs_lookup errors > > > > > > > > > with 6.3.2-rc2 (I have not seen this error before.) No other errors in the logs. > > > > > > > > > > > > > > > > Can you reproduce this without the extern, gpl-violation module loaded? > > > > > > > > > > > > > > > > thanks, > > > > > > > > > > > > > > > > greg k-h > > > > > > > > > > > > > > Hi Greg, > > > > > > > > > > > > > > I dropped the bcm_sta and recompiled and commented out the i915.guc=3 > > > > > > > and was able to reproduce. > > > > > > > > > > > > > > [ 84.745080] BUG: kernel NULL pointer dereference, address: 0000000000000020 > > > > > > > [ 84.746239] #PF: supervisor read access in kernel mode > > > > > > > [ 84.747599] #PF: error_code(0x0000) - not-present page > > > > > > > [ 84.748929] PGD 0 P4D 0 > > > > > > > [ 84.750240] Oops: 0000 [#1] SMP NOPTI > > > > > > > [ 84.751575] CPU: 2 PID: 3176 Comm: .NET ThreadPool Not tainted 6.3.2-rc2 #1 > > > > > > > [ 84.752998] Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > > > > > > > [ 84.754474] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] > > > > > > > > > > > > And do you get this same crash on ntfs3 on 6.4-rc1? Is this a new > > > > > > regression, or does it also show up on 6.3.1? > > > > > > > > > > Tested with 6.3.1 during the day today. No errors, and had been > > > > > running 6.3.1 with no issue. Retested with 6.3.2-rc2 and problem > > > > > immediately evident. So yes - I believe a regression. > > > > > > > > > > I have built and am now testing 6.4.0-rc1 this evening - no errors so far. > > > > > > > > > > [ 0.000000] Linux version 6.4.0-rc1 (docker@1ccd349e2545) > > > > > (x86_64-libreelec-linux-gnu-gcc-13.1.0 (GCC) 13.1.0, GNU ld (GNU > > > > > Binutils) 2.40) #1 SMP Wed May 10 07:51:37 UTC 2023 > > > > > > > > > > > And ntfs, ick, why? And .NET? What a combination... > > > > > > > > > > Joys of media players. Test device gets to test exfat, ntfs3, .NET, > > > > > and throw in a compile host/GHA runner to put it through paces. > > > > > > > > Yeah, this should work. Thanks for verifying this works on other > > > > releases. Any chance you can do 'git bisect' to track down the > > > > offending commit? In looking things over, I don't see anything > > > > obvious... > > > > > > Hi Greg, > > > > > > I can confirm the offending commit in 6.3.2-rc2 is > > > > > > bf11fd528a97 fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup() > > > > Thanks! Odd that this didn't show up for you on the other stable -rc > > releases, as that commit is also in those trees. > > > > I'll go revert this for now and ask the maintainer to send a fixed > > version. > > Hi Greg, > > I have run 6.1.28-rc2 today, and was able to trigger the error. So > definitely bad in both 6.3 and 6.1. > > [13812.020209] BUG: kernel NULL pointer dereference, address: 0000000000000020 > [13812.021322] #PF: supervisor read access in kernel mode > [13812.022346] #PF: error_code(0x0000) - not-present page > [13812.023591] PGD 0 P4D 0 > [13812.024876] Oops: 0000 [#1] SMP NOPTI > [13812.026088] CPU: 5 PID: 20386 Comm: .NET ThreadPool Not tainted 6.1.28-rc2 #1 > [13812.027336] Hardware name: Intel(R) Client Systems > NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > [13812.028593] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] > [13812.029827] Code: 00 00 00 49 89 c4 e8 19 47 fe ff 85 c0 79 3a 48 > 63 d8 48 8b 3d 4b 1d 77 cd 4c 89 e6 e8 33 25 d1 c3 48 81 fb 00 f0 ff > ff 77 07 <48> 83 7b 20 00 74 41 4c 89 ee 48 89 df e8 88 a5 d5 c3 5b 41 > 5c 41 > [13812.031149] RSP: 0018:ffff91f40537bbc8 EFLAGS: 00010207 > [13812.032408] RAX: ffff8a844946a001 RBX: 0000000000000000 RCX: 00000000000042f7 > [13812.033650] RDX: 00000000000042f6 RSI: fffff40a00000000 RDI: 0000000000030ed0 > [13812.034869] RBP: ffff91f40537bbe8 R08: ffff8a844946c01e R09: ffff8a8474d0387e > [13812.036138] R10: ffff8a845a900000 R11: 0000000000000017 R12: ffff8a844946c000 > [13812.037372] R13: ffff8a84db3fd2c0 R14: ffff8a84b44a0470 R15: ffff8a84b44a0548 > [13812.039002] FS: 00007f437e7fc6c0(0000) GS:ffff8a8b77740000(0000) > knlGS:0000000000000000 > [13812.040509] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > [13812.041741] CR2: 0000000000000020 CR3: 000000017835e006 CR4: 0000000000f70ea0 > [13812.042986] PKRU: 55555554 > [13812.044227] Call Trace: > [13812.045464] <TASK> > [13812.046708] __lookup_slow+0x81/0x130 > [13812.047939] walk_component+0x10b/0x180 > [13812.049169] path_lookupat+0x6a/0x1a0 > [13812.050388] filename_lookup+0xd0/0x190 > [13812.051612] vfs_statx+0x84/0x150 > [13812.052838] ? getname_flags+0x54/0x1d0 > [13812.054062] vfs_fstatat+0x5c/0x80 > [13812.055284] __do_sys_newlstat+0x37/0x70 > [13812.056580] ? trace_hardirqs_on+0x3a/0xe0 > [13812.058429] __x64_sys_newlstat+0x1a/0x20 > [13812.059878] do_syscall_64+0x3c/0x90 > [13812.061109] entry_SYSCALL_64_after_hwframe+0x63/0xcd > [13812.062369] RIP: 0033:0x7f447ea17184 > [13812.063598] Code: 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 > 00 00 0f 1f 40 00 89 f8 48 89 f7 48 89 d6 83 f8 01 77 2b b8 06 00 00 > 00 0f 05 <48> 3d 00 f0 ff ff 77 04 c3 0f 1f 00 48 8b 15 61 cc 0b 00 f7 > d8 64 > [13812.064927] RSP: 002b:00007f437e7fa098 EFLAGS: 00000246 ORIG_RAX: > 0000000000000006 > [13812.066267] RAX: ffffffffffffffda RBX: 00007f43cf45a870 RCX: 00007f447ea17184 > [13812.067601] RDX: 00007f437e7fa0a0 RSI: 00007f437e7fa0a0 RDI: 00007f437e7fa210 > [13812.068940] RBP: 00007f437e7fa1f0 R08: 00007f437e7fa320 R09: 000000000000002d > [13812.070276] R10: 00007f44051a15e8 R11: 0000000000000246 R12: 00007f43cc018408 > [13812.071616] R13: 00007f437e7fa210 R14: 00007f43cf45a870 R15: 000000000000002d > [13812.072960] </TASK> > [13812.074295] Modules linked in: rfcomm xt_nat xt_tcpudp veth > xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat > nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype > iptable_filter ip_tables x_tables br_netfilter bridge stp llc overlay > 8021q ntfs3 bnep btusb btrtl btbcm btintel btmtk bluetooth > ecdh_generic ecc exfat snd_hda_codec_hdmi snd_hda_codec_realtek > snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_hda_codec > iwlwifi mei_hdcp snd_hwdep tpm_tis mei_pxp x86_pkg_temp_thermal > snd_hda_core tpm_tis_core cfg80211 intel_rapl_msr mei_me > intel_powerclamp snd_intel_dspcfg intel_rapl_common mei rfkill tpm_crb > idma64 tpm rng_core pkcs8_key_parser fuse dmi_sysfs > [13812.079600] CR2: 0000000000000020 > [13812.081160] ---[ end trace 0000000000000000 ]--- Wonderful, thanks for testing this out! Hopefully the real releases in a bit are all good, thanks for letting us know. greg k-h ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-11 8:30 ` Rudi Heitbaum 2023-05-11 13:33 ` Greg Kroah-Hartman @ 2023-05-11 14:19 ` Linus Torvalds 2023-05-12 9:59 ` Rudi Heitbaum 1 sibling, 1 reply; 14+ messages in thread From: Linus Torvalds @ 2023-05-11 14:19 UTC (permalink / raw) To: Rudi Heitbaum Cc: Greg Kroah-Hartman, stable, patches, linux-kernel, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Thu, May 11, 2023 at 3:30 AM Rudi Heitbaum <rudi@heitbaum.com> wrote: > > I have run 6.1.28-rc2 today, and was able to trigger the error. So > definitely bad in both 6.3 and 6.1. > > [13812.020209] BUG: kernel NULL pointer dereference, address: 0000000000000020 > [13812.021322] #PF: supervisor read access in kernel mode > [13812.022346] #PF: error_code(0x0000) - not-present page > [13812.023591] PGD 0 P4D 0 > [13812.024876] Oops: 0000 [#1] SMP NOPTI > [13812.026088] CPU: 5 PID: 20386 Comm: .NET ThreadPool Not tainted 6.1.28-rc2 #1 > [13812.027336] Hardware name: Intel(R) Client Systems > NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > [13812.028593] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] I suspect this is fixed in mainline by commit 6827d50b2c43 ("fs/ntfs3: Refactoring of various minor issues") which changed the IS_ERR() check into a IS_ERR_OR_NULL(). But dropping the original fix from stable might be the right thing to do. Linus ^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH 6.3 000/694] 6.3.2-rc2 review 2023-05-11 14:19 ` Linus Torvalds @ 2023-05-12 9:59 ` Rudi Heitbaum 0 siblings, 0 replies; 14+ messages in thread From: Rudi Heitbaum @ 2023-05-12 9:59 UTC (permalink / raw) To: Linus Torvalds Cc: Greg Kroah-Hartman, stable, patches, linux-kernel, akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw, rwarsow, ntfs3, almaz.alexandrovich On Fri, 12 May 2023 at 00:24, Linus Torvalds <torvalds@linux-foundation.org> wrote: > > On Thu, May 11, 2023 at 3:30 AM Rudi Heitbaum <rudi@heitbaum.com> wrote: > > > > I have run 6.1.28-rc2 today, and was able to trigger the error. So > > definitely bad in both 6.3 and 6.1. > > > > [13812.020209] BUG: kernel NULL pointer dereference, address: 0000000000000020 > > [13812.021322] #PF: supervisor read access in kernel mode > > [13812.022346] #PF: error_code(0x0000) - not-present page > > [13812.023591] PGD 0 P4D 0 > > [13812.024876] Oops: 0000 [#1] SMP NOPTI > > [13812.026088] CPU: 5 PID: 20386 Comm: .NET ThreadPool Not tainted 6.1.28-rc2 #1 > > [13812.027336] Hardware name: Intel(R) Client Systems > > NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0085.2022.0718.1739 07/18/2022 > > [13812.028593] RIP: 0010:ntfs_lookup+0x76/0xe0 [ntfs3] > > I suspect this is fixed in mainline by commit 6827d50b2c43 ("fs/ntfs3: > Refactoring of various minor issues") which changed the IS_ERR() check > into a IS_ERR_OR_NULL(). Hi Linus, Thanks for the direction to the commit. I can confirm that once adding commit 6827d50b2c43 to both 6.1.28-rc2 and 6.3.2-rc2 and testing for today - that the error is not reproducible with the below lines. - if (!IS_ERR(inode) && inode->i_op == NULL) { + if (!IS_ERR_OR_NULL(inode) && !inode->i_op) { Rudi > But dropping the original fix from stable might be the right thing to do. > > Linus ^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2023-05-12 9:59 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20230509030705.399628514@linuxfoundation.org>
[not found] ` <20230509080658.GA152864@d6921c044a31>
2023-05-09 13:10 ` [PATCH 6.3 000/694] 6.3.2-rc2 review Rudi Heitbaum
2023-05-09 13:56 ` Greg Kroah-Hartman
2023-05-09 14:58 ` Rudi Heitbaum
2023-05-09 19:30 ` Naresh Kamboju
2023-05-10 6:53 ` Rudi Heitbaum
2023-05-10 7:25 ` Greg Kroah-Hartman
2023-05-10 8:29 ` Rudi Heitbaum
2023-05-10 9:09 ` Greg Kroah-Hartman
2023-05-10 11:58 ` Rudi Heitbaum
2023-05-10 23:00 ` Greg Kroah-Hartman
2023-05-11 8:30 ` Rudi Heitbaum
2023-05-11 13:33 ` Greg Kroah-Hartman
2023-05-11 14:19 ` Linus Torvalds
2023-05-12 9:59 ` Rudi Heitbaum
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox