linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [syzbot]
  2022-02-10 19:17 [syzbot] general protection fault in blk_mq_free_rqs syzbot
@ 2023-11-10 18:56 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-10 18:56 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: yuran.pereira@hotmail.com

#syz test: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master

^ permalink raw reply	[flat|nested] 144+ messages in thread

* [syzbot] [dri?] divide error in drm_mode_debug_printmodeline
@ 2023-11-15  9:34 syzbot
  2023-11-16  0:52 ` [syzbot] [PATCH] test " syzbot
                   ` (12 more replies)
  0 siblings, 13 replies; 144+ messages in thread
From: syzbot @ 2023-11-15  9:34 UTC (permalink / raw)
  To: airlied, airlied, daniel.vetter, daniel.vetter, daniel, dri-devel,
	linux-kernel, maarten.lankhorst, melissa.srw, mripard,
	syzkaller-bugs, tzimmermann

Hello,

syzbot found the following issue on:

HEAD commit:    ac347a0655db Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=101ba588e80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=88e7ba51eecd9cd6
dashboard link: https://syzkaller.appspot.com/bug?extid=2e93e6fb36e6fdc56574
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11252f97680000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10fd2498e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8fcb90d89768/disk-ac347a06.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/360d9341a71c/vmlinux-ac347a06.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a370aa406c63/bzImage-ac347a06.xz

The issue was bisected to:

commit ea40d7857d5250e5400f38c69ef9e17321e9c4a2
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Oct 9 23:21:56 2020 +0000

    drm/vkms: fbdev emulation support

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1058223f680000
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1258223f680000
console output: https://syzkaller.appspot.com/x/log.txt?x=1458223f680000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2e93e6fb36e6fdc56574@syzkaller.appspotmail.com
Fixes: ea40d7857d52 ("drm/vkms: fbdev emulation support")

divide error: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5068 Comm: syz-executor357 Not tainted 6.6.0-syzkaller-16039-gac347a0655db #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
RIP: 0010:drm_mode_vrefresh drivers/gpu/drm/drm_modes.c:1303 [inline]
RIP: 0010:drm_mode_debug_printmodeline+0x118/0x4e0 drivers/gpu/drm/drm_modes.c:60
Code: 00 41 0f b7 07 66 83 f8 02 b9 01 00 00 00 0f 43 c8 0f b7 c1 0f af e8 44 89 f0 48 69 c8 e8 03 00 00 89 e8 d1 e8 48 01 c8 31 d2 <48> f7 f5 49 89 c6 eb 0c e8 fb 07 66 fc eb 05 e8 f4 07 66 fc 48 89
RSP: 0018:ffffc9000391f8d0 EFLAGS: 00010246
RAX: 000000000001f400 RBX: ffff888025045000 RCX: 000000000001f400
RDX: 0000000000000000 RSI: 0000000000008000 RDI: ffff888025045018
RBP: 0000000000000000 R08: ffffffff8528b9af R09: 0000000000000000
R10: ffffc9000391f8a0 R11: fffff52000723f17 R12: 0000000000000080
R13: dffffc0000000000 R14: 0000000000000080 R15: ffff888025045016
FS:  0000555556932380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000005fdeb8 CR3: 000000007fcff000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 drm_mode_setcrtc+0x83b/0x1880 drivers/gpu/drm/drm_crtc.c:794
 drm_ioctl_kernel+0x362/0x500 drivers/gpu/drm/drm_ioctl.c:792
 drm_ioctl+0x636/0xb00 drivers/gpu/drm/drm_ioctl.c:895
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:871 [inline]
 __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:857
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f6c63dd6729
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcde0dd0e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ffcde0dd2b8 RCX: 00007f6c63dd6729
RDX: 0000000020000180 RSI: 00000000c06864a2 RDI: 0000000000000003
RBP: 00007f6c63e49610 R08: 00000000fffff4e6 R09: 00007ffcde0dd2b8
R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffcde0dd2a8 R14: 0000000000000001 R15: 0000000000000001
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:drm_mode_vrefresh drivers/gpu/drm/drm_modes.c:1303 [inline]
RIP: 0010:drm_mode_debug_printmodeline+0x118/0x4e0 drivers/gpu/drm/drm_modes.c:60
Code: 00 41 0f b7 07 66 83 f8 02 b9 01 00 00 00 0f 43 c8 0f b7 c1 0f af e8 44 89 f0 48 69 c8 e8 03 00 00 89 e8 d1 e8 48 01 c8 31 d2 <48> f7 f5 49 89 c6 eb 0c e8 fb 07 66 fc eb 05 e8 f4 07 66 fc 48 89
RSP: 0018:ffffc9000391f8d0 EFLAGS: 00010246
RAX: 000000000001f400 RBX: ffff888025045000 RCX: 000000000001f400
RDX: 0000000000000000 RSI: 0000000000008000 RDI: ffff888025045018
RBP: 0000000000000000 R08: ffffffff8528b9af R09: 0000000000000000
R10: ffffc9000391f8a0 R11: fffff52000723f17 R12: 0000000000000080
R13: dffffc0000000000 R14: 0000000000000080 R15: ffff888025045016
FS:  0000555556932380(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000064392c CR3: 000000007fcff000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	00 41 0f             	add    %al,0xf(%rcx)
   3:	b7 07                	mov    $0x7,%bh
   5:	66 83 f8 02          	cmp    $0x2,%ax
   9:	b9 01 00 00 00       	mov    $0x1,%ecx
   e:	0f 43 c8             	cmovae %eax,%ecx
  11:	0f b7 c1             	movzwl %cx,%eax
  14:	0f af e8             	imul   %eax,%ebp
  17:	44 89 f0             	mov    %r14d,%eax
  1a:	48 69 c8 e8 03 00 00 	imul   $0x3e8,%rax,%rcx
  21:	89 e8                	mov    %ebp,%eax
  23:	d1 e8                	shr    %eax
  25:	48 01 c8             	add    %rcx,%rax
  28:	31 d2                	xor    %edx,%edx
* 2a:	48 f7 f5             	div    %rbp <-- trapping instruction
  2d:	49 89 c6             	mov    %rax,%r14
  30:	eb 0c                	jmp    0x3e
  32:	e8 fb 07 66 fc       	call   0xfc660832
  37:	eb 05                	jmp    0x3e
  39:	e8 f4 07 66 fc       	call   0xfc660832
  3e:	48                   	rex.W
  3f:	89                   	.byte 0x89


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot] [PATCH] test divide error in drm_mode_debug_printmodeline
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
@ 2023-11-16  0:52 ` syzbot
  2023-11-16  2:33 ` [syzbot] syzbot
                   ` (11 subsequent siblings)
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-16  0:52 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] test divide error in drm_mode_debug_printmodeline
Author: lizhi.xu@windriver.com

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ac347a0655db

diff --git a/include/drm/drm_modes.h b/include/drm/drm_modes.h
index c613f0abe9dc..19e37e92dfaf 100644
--- a/include/drm/drm_modes.h
+++ b/include/drm/drm_modes.h
@@ -422,7 +422,7 @@ struct drm_display_mode {
 /**
  * DRM_MODE_FMT - printf string for &struct drm_display_mode
  */
-#define DRM_MODE_FMT    "\"%s\": %d %d %d %d %d %d %d %d %d %d 0x%x 0x%x"
+#define DRM_MODE_FMT    "\"%s\": %llu %d %d %d %d %d %d %d %d %d 0x%x 0x%x"
 
 /**
  * DRM_MODE_ARG - printf arguments for &struct drm_display_mode
@@ -526,7 +526,7 @@ static inline int of_get_drm_panel_display_mode(struct device_node *np,
 #endif
 
 void drm_mode_set_name(struct drm_display_mode *mode);
-int drm_mode_vrefresh(const struct drm_display_mode *mode);
+long drm_mode_vrefresh(const struct drm_display_mode *mode);
 void drm_mode_get_hv_timing(const struct drm_display_mode *mode,
 			    int *hdisplay, int *vdisplay);
 
diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
index ac9a406250c5..6f376001728c 100644
--- a/drivers/gpu/drm/drm_modes.c
+++ b/drivers/gpu/drm/drm_modes.c
@@ -1283,9 +1283,9 @@ EXPORT_SYMBOL(drm_mode_set_name);
  * @modes's vrefresh rate in Hz, rounded to the nearest integer. Calculates the
  * value first if it is not yet set.
  */
-int drm_mode_vrefresh(const struct drm_display_mode *mode)
+long drm_mode_vrefresh(const struct drm_display_mode *mode)
 {
-	unsigned int num, den;
+	unsigned long num, den;
 
 	if (mode->htotal == 0 || mode->vtotal == 0)
 		return 0;

^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
  2023-11-16  0:52 ` [syzbot] [PATCH] test " syzbot
@ 2023-11-16  2:33 ` syzbot
  2023-11-16  3:29 ` [syzbot] syzbot
                   ` (10 subsequent siblings)
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-16  2:33 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: mazinalhaddad05@gmail.com

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
  2023-11-16  0:52 ` [syzbot] [PATCH] test " syzbot
  2023-11-16  2:33 ` [syzbot] syzbot
@ 2023-11-16  3:29 ` syzbot
  2023-11-18  3:42 ` [syzbot] [PATCH] Test divide err in drm syzbot
                   ` (9 subsequent siblings)
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-16  3:29 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: mazinalhaddad05@gmail.com

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot] [PATCH] Test divide err in drm
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
                   ` (2 preceding siblings ...)
  2023-11-16  3:29 ` [syzbot] syzbot
@ 2023-11-18  3:42 ` syzbot
  2023-11-18  6:44 ` syzbot
                   ` (8 subsequent siblings)
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-18  3:42 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] Test divide err in drm
Author: eadavis@qq.com

please test divide err in drm

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 888cf78c29e2

diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
index ac9a406250c5..e3f05539f704 100644
--- a/drivers/gpu/drm/drm_modes.c
+++ b/drivers/gpu/drm/drm_modes.c
@@ -1283,9 +1283,9 @@ EXPORT_SYMBOL(drm_mode_set_name);
  * @modes's vrefresh rate in Hz, rounded to the nearest integer. Calculates the
  * value first if it is not yet set.
  */
-int drm_mode_vrefresh(const struct drm_display_mode *mode)
+long drm_mode_vrefresh(const struct drm_display_mode *mode)
 {
-	unsigned int num, den;
+	unsigned long num, den;
 
 	if (mode->htotal == 0 || mode->vtotal == 0)
 		return 0;
@@ -1300,6 +1300,8 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
 	if (mode->vscan > 1)
 		den *= mode->vscan;
 
+	printk("mode: %p, ht: %llu, vt: %llu, c: %llu, vsc: %llu, den: %llu, num: %llu, %s", 
+		mode, mode->htotal, mode->vtotal, mode->clock, mode->vscan, den, num, __func__);
 	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 }
 EXPORT_SYMBOL(drm_mode_vrefresh);
diff --git a/include/drm/drm_modes.h b/include/drm/drm_modes.h
index c613f0abe9dc..19e37e92dfaf 100644
--- a/include/drm/drm_modes.h
+++ b/include/drm/drm_modes.h
@@ -422,7 +422,7 @@ struct drm_display_mode {
 /**
  * DRM_MODE_FMT - printf string for &struct drm_display_mode
  */
-#define DRM_MODE_FMT    "\"%s\": %d %d %d %d %d %d %d %d %d %d 0x%x 0x%x"
+#define DRM_MODE_FMT    "\"%s\": %llu %d %d %d %d %d %d %d %d %d 0x%x 0x%x"
 
 /**
  * DRM_MODE_ARG - printf arguments for &struct drm_display_mode
@@ -526,7 +526,7 @@ static inline int of_get_drm_panel_display_mode(struct device_node *np,
 #endif
 
 void drm_mode_set_name(struct drm_display_mode *mode);
-int drm_mode_vrefresh(const struct drm_display_mode *mode);
+long drm_mode_vrefresh(const struct drm_display_mode *mode);
 void drm_mode_get_hv_timing(const struct drm_display_mode *mode,
 			    int *hdisplay, int *vdisplay);
 


^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [syzbot] [PATCH] Test divide err in drm
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
                   ` (3 preceding siblings ...)
  2023-11-18  3:42 ` [syzbot] [PATCH] Test divide err in drm syzbot
@ 2023-11-18  6:44 ` syzbot
  2023-11-18 10:29 ` syzbot
                   ` (7 subsequent siblings)
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-18  6:44 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] Test divide err in drm
Author: eadavis@qq.com

please test divide err in drm

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ac347a0655db

diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
index ac9a406250c5..0b0dd1c7b217 100644
--- a/drivers/gpu/drm/drm_modes.c
+++ b/drivers/gpu/drm/drm_modes.c
@@ -1285,7 +1285,7 @@ EXPORT_SYMBOL(drm_mode_set_name);
  */
 int drm_mode_vrefresh(const struct drm_display_mode *mode)
 {
-	unsigned int num, den;
+	unsigned int num, den, n1k;
 
 	if (mode->htotal == 0 || mode->vtotal == 0)
 		return 0;
@@ -1297,9 +1297,14 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
 		num *= 2;
 	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
 		den *= 2;
-	if (mode->vscan > 1)
-		den *= mode->vscan;
+	if (mode->vscan > 1) {
+		n1k = mul_u32_u32(num, 1000);
+		if (den < n1k)
+			den *= mode->vscan;
+	}
 
+	printk("mode: %p, ht: %d, vt: %d, c: %d, vsc: %d, den: %ld, num: %ld, n1k: %ld, %s", 
+		mode, mode->htotal, mode->vtotal, mode->clock, mode->vscan, den, num, n1k, __func__);
 	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 }
 EXPORT_SYMBOL(drm_mode_vrefresh);


^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [syzbot] [PATCH] Test divide err in drm
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
                   ` (4 preceding siblings ...)
  2023-11-18  6:44 ` syzbot
@ 2023-11-18 10:29 ` syzbot
  2023-11-18 11:59 ` syzbot
                   ` (6 subsequent siblings)
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-18 10:29 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] Test divide err in drm
Author: eadavis@qq.com

please test divide err in drm

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ac347a0655db

diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
index ac9a406250c5..ca481c7f23e1 100644
--- a/drivers/gpu/drm/drm_modes.c
+++ b/drivers/gpu/drm/drm_modes.c
@@ -1285,7 +1285,8 @@ EXPORT_SYMBOL(drm_mode_set_name);
  */
 int drm_mode_vrefresh(const struct drm_display_mode *mode)
 {
-	unsigned int num, den;
+	unsigned int num, den, n1k;
+	int ret;
 
 	if (mode->htotal == 0 || mode->vtotal == 0)
 		return 0;
@@ -1297,9 +1298,15 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
 		num *= 2;
 	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
 		den *= 2;
-	if (mode->vscan > 1)
-		den *= mode->vscan;
+	if (mode->vscan > 1) {
+		n1k = mul_u32_u32(num, 1000);
+		if (den < n1k)
+			den *= mode->vscan;
+	}
+	ret = DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 
+	printk("mode: %p, ht: %d, vt: %d, c: %d, vsc: %d, den: %ld, num: %ld, n1k: %ld, %d, %s", 
+		mode, mode->htotal, mode->vtotal, mode->clock, mode->vscan, den, num, n1k, ret, __func__);
 	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 }
 EXPORT_SYMBOL(drm_mode_vrefresh);


^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [syzbot] [PATCH] Test divide err in drm
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
                   ` (5 preceding siblings ...)
  2023-11-18 10:29 ` syzbot
@ 2023-11-18 11:59 ` syzbot
  2023-11-19  1:31 ` syzbot
                   ` (5 subsequent siblings)
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-18 11:59 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] Test divide err in drm
Author: eadavis@qq.com

please test divide err in drm

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ac347a0655db

diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
index ac9a406250c5..539aa26cfc72 100644
--- a/drivers/gpu/drm/drm_modes.c
+++ b/drivers/gpu/drm/drm_modes.c
@@ -1285,7 +1285,8 @@ EXPORT_SYMBOL(drm_mode_set_name);
  */
 int drm_mode_vrefresh(const struct drm_display_mode *mode)
 {
-	unsigned int num, den;
+	unsigned int num, den, n1k;
+	int ret;
 
 	if (mode->htotal == 0 || mode->vtotal == 0)
 		return 0;
@@ -1297,9 +1298,17 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
 		num *= 2;
 	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
 		den *= 2;
-	if (mode->vscan > 1)
-		den *= mode->vscan;
+	n1k = mul_u32_u32(num, 1000);
+	if (mode->vscan > 1) {
+		if (den < n1k)
+			den *= mode->vscan;
+	}
+	if (den < n1k)
+		den = n1k + 1;
+	ret = DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 
+	printk("mode: %p, ht: %d, vt: %d, c: %d, vsc: %d, den: %ld, num: %ld, n1k: %ld, %d, %s", 
+		mode, mode->htotal, mode->vtotal, mode->clock, mode->vscan, den, num, n1k, ret, __func__);
 	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 }
 EXPORT_SYMBOL(drm_mode_vrefresh);


^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [syzbot] [PATCH] Test divide err in drm
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
                   ` (6 preceding siblings ...)
  2023-11-18 11:59 ` syzbot
@ 2023-11-19  1:31 ` syzbot
       [not found] ` <tencent_F6C990AEE12ED34C8467CBC6FBD2F4467F06@qq.com>
                   ` (4 subsequent siblings)
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-19  1:31 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] Test divide err in drm
Author: eadavis@qq.com

please test divide err in drm

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ac347a0655db

diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
index ac9a406250c5..1a3e8f3c1ece 100644
--- a/drivers/gpu/drm/drm_modes.c
+++ b/drivers/gpu/drm/drm_modes.c
@@ -36,6 +36,7 @@
 #include <linux/list.h>
 #include <linux/list_sort.h>
 #include <linux/of.h>
+#include <linux/log2.h>
 
 #include <video/of_display_timing.h>
 #include <video/of_videomode.h>
@@ -1297,8 +1298,12 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
 		num *= 2;
 	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
 		den *= 2;
-	if (mode->vscan > 1)
+	if (mode->vscan > 1) {
+		printk("%d, %d, %s\n", ilog2(den), ilog2(mode->vscan), __func__);
+		if (ilog2(den) + ilog2(mode->vscan) >= 32)
+			return -EINVAL;
 		den *= mode->vscan;
+	}
 
 	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 }


^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [PATCH] drm/modes: Fix divide error in drm_mode_debug_printmodeline
       [not found] ` <tencent_F6C990AEE12ED34C8467CBC6FBD2F4467F06@qq.com>
@ 2023-11-20 11:31   ` Jani Nikula
       [not found]     ` <tencent_DCCE6C78766FE82D816F9C94F0EAC2ED260A@qq.com>
  0 siblings, 1 reply; 144+ messages in thread
From: Jani Nikula @ 2023-11-20 11:31 UTC (permalink / raw)
  To: Edward Adam Davis, syzbot+2e93e6fb36e6fdc56574
  Cc: tzimmermann, airlied, daniel.vetter, linux-kernel, dri-devel,
	melissa.srw, mripard, daniel.vetter, syzkaller-bugs

On Sun, 19 Nov 2023, Edward Adam Davis <eadavis@qq.com> wrote:
> [Syz Log]
> divide error: 0000 [#1] PREEMPT SMP KASAN
> CPU: 0 PID: 5068 Comm: syz-executor357 Not tainted 6.6.0-syzkaller-16039-gac347a0655db #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
> RIP: 0010:drm_mode_vrefresh drivers/gpu/drm/drm_modes.c:1303 [inline]
> RIP: 0010:drm_mode_debug_printmodeline+0x118/0x4e0 drivers/gpu/drm/drm_modes.c:60
> Code: 00 41 0f b7 07 66 83 f8 02 b9 01 00 00 00 0f 43 c8 0f b7 c1 0f af e8 44 89 f0 48 69 c8 e8 03 00 00 89 e8 d1 e8 48 01 c8 31 d2 <48> f7 f5 49 89 c6 eb 0c e8 fb 07 66 fc eb 05 e8 f4 07 66 fc 48 89
> RSP: 0018:ffffc9000391f8d0 EFLAGS: 00010246
> RAX: 000000000001f400 RBX: ffff888025045000 RCX: 000000000001f400
> RDX: 0000000000000000 RSI: 0000000000008000 RDI: ffff888025045018
> RBP: 0000000000000000 R08: ffffffff8528b9af R09: 0000000000000000
> R10: ffffc9000391f8a0 R11: fffff52000723f17 R12: 0000000000000080
> R13: dffffc0000000000 R14: 0000000000000080 R15: ffff888025045016
> FS:  0000555556932380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00000000005fdeb8 CR3: 000000007fcff000 CR4: 00000000003506f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
>  <TASK>
>  drm_mode_setcrtc+0x83b/0x1880 drivers/gpu/drm/drm_crtc.c:794
>  drm_ioctl_kernel+0x362/0x500 drivers/gpu/drm/drm_ioctl.c:792
>  drm_ioctl+0x636/0xb00 drivers/gpu/drm/drm_ioctl.c:895
>  vfs_ioctl fs/ioctl.c:51 [inline]
>  __do_sys_ioctl fs/ioctl.c:871 [inline]
>  __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:857
>  do_syscall_x64 arch/x86/entry/common.c:51 [inline]
>  do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
>  entry_SYSCALL_64_after_hwframe+0x63/0x6b
>
> [Analysis]
> When calculating den in drm_mode_vrefresh(), if the vscan value is too large, 
> there is a probability of unsigned integer overflow.
>
> [Fix]
> Before multiplying by vscan, first determine their ilog2. When their total 
> exceeds 32, return -EINVAL and exit the subsequent calculation.
>
> Reported-and-tested-by: syzbot+2e93e6fb36e6fdc56574@syzkaller.appspotmail.com
> Fixes: ea40d7857d52 ("drm/vkms: fbdev emulation support")
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
> ---
>  drivers/gpu/drm/drm_modes.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
> index ac9a406250c5..c7ec1ab041f8 100644
> --- a/drivers/gpu/drm/drm_modes.c
> +++ b/drivers/gpu/drm/drm_modes.c
> @@ -36,6 +36,7 @@
>  #include <linux/list.h>
>  #include <linux/list_sort.h>
>  #include <linux/of.h>
> +#include <linux/log2.h>
>  
>  #include <video/of_display_timing.h>
>  #include <video/of_videomode.h>
> @@ -1297,8 +1298,11 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
>  		num *= 2;
>  	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
>  		den *= 2;
> -	if (mode->vscan > 1)
> +	if (mode->vscan > 1) {
> +		if (ilog2(den) + ilog2(mode->vscan) >= 32)

For future reference, check_mul_overflow() is the way to handle this.

> +			return -EINVAL;

Just so there's no confusion: NAK.

I'd be surprised if there were even a single place in the kernel where
someone checks drm_mode_vrefresh() for a negative error return.

This function must succeed.

Please change the types as needed instead.


BR,
Jani.

>  		den *= mode->vscan;
> +	}
>  
>  	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
>  }

-- 
Jani Nikula, Intel

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot] [PATCH] Test divide err in drm
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
                   ` (8 preceding siblings ...)
       [not found] ` <tencent_F6C990AEE12ED34C8467CBC6FBD2F4467F06@qq.com>
@ 2023-11-20 12:00 ` syzbot
  2023-11-20 12:22 ` syzbot
                   ` (2 subsequent siblings)
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-20 12:00 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] Test divide err in drm
Author: eadavis@qq.com

please test divide err in drm

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ac347a0655db

diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
index ac9a406250c5..117ee4e41c63 100644
--- a/drivers/gpu/drm/drm_modes.c
+++ b/drivers/gpu/drm/drm_modes.c
@@ -36,6 +36,7 @@
 #include <linux/list.h>
 #include <linux/list_sort.h>
 #include <linux/of.h>
+#include <linux/overflow.h>
 
 #include <video/of_display_timing.h>
 #include <video/of_videomode.h>
@@ -1297,8 +1298,11 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
 		num *= 2;
 	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
 		den *= 2;
-	if (mode->vscan > 1)
+	if (mode->vscan > 1) {
+		if (unlikely(check_mul_overflow(den, mode->vscan, &den)))
+			return 0;
 		den *= mode->vscan;
+	}
 
 	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 }


^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [syzbot] [PATCH] Test divide err in drm
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
                   ` (9 preceding siblings ...)
  2023-11-20 12:00 ` [syzbot] [PATCH] Test divide err in drm syzbot
@ 2023-11-20 12:22 ` syzbot
  2023-11-20 13:30 ` syzbot
  2025-01-18 18:25 ` [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-20 12:22 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] Test divide err in drm
Author: eadavis@qq.com

please test divide err in drm

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ac347a0655db

diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
index ac9a406250c5..7c6d0229630d 100644
--- a/drivers/gpu/drm/drm_modes.c
+++ b/drivers/gpu/drm/drm_modes.c
@@ -36,6 +36,7 @@
 #include <linux/list.h>
 #include <linux/list_sort.h>
 #include <linux/of.h>
+#include <linux/overflow.h>
 
 #include <video/of_display_timing.h>
 #include <video/of_videomode.h>
@@ -1285,7 +1286,7 @@ EXPORT_SYMBOL(drm_mode_set_name);
  */
 int drm_mode_vrefresh(const struct drm_display_mode *mode)
 {
-	unsigned int num, den;
+	unsigned int num, den, x;
 
 	if (mode->htotal == 0 || mode->vtotal == 0)
 		return 0;
@@ -1297,8 +1298,11 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
 		num *= 2;
 	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
 		den *= 2;
-	if (mode->vscan > 1)
+	if (mode->vscan > 1) {
+		if (unlikely(check_mul_overflow(den, mode->vscan, &x)))
+			return 0;
 		den *= mode->vscan;
+	}
 
 	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 }


^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [syzbot] [PATCH] Test divide err in drm
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
                   ` (10 preceding siblings ...)
  2023-11-20 12:22 ` syzbot
@ 2023-11-20 13:30 ` syzbot
  2025-01-18 18:25 ` [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-20 13:30 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [PATCH] Test divide err in drm
Author: eadavis@qq.com

please test divide err in drm

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ac347a0655db

diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
index ac9a406250c5..60739d861da2 100644
--- a/drivers/gpu/drm/drm_modes.c
+++ b/drivers/gpu/drm/drm_modes.c
@@ -36,6 +36,7 @@
 #include <linux/list.h>
 #include <linux/list_sort.h>
 #include <linux/of.h>
+#include <linux/overflow.h>
 
 #include <video/of_display_timing.h>
 #include <video/of_videomode.h>
@@ -1297,8 +1298,10 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
 		num *= 2;
 	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
 		den *= 2;
-	if (mode->vscan > 1)
-		den *= mode->vscan;
+	if (mode->vscan > 1) {
+		if (unlikely(check_mul_overflow(den, mode->vscan, &den)))
+			return 0;
+	}
 
 	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
 }


^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [PATCH V2] drm/modes: Fix divide error in drm_mode_debug_printmodeline
       [not found]     ` <tencent_DCCE6C78766FE82D816F9C94F0EAC2ED260A@qq.com>
@ 2023-11-20 15:12       ` Ville Syrjälä
  2023-11-21  9:20         ` Jani Nikula
  0 siblings, 1 reply; 144+ messages in thread
From: Ville Syrjälä @ 2023-11-20 15:12 UTC (permalink / raw)
  To: Edward Adam Davis
  Cc: jani.nikula, airlied, daniel.vetter, linux-kernel, dri-devel,
	melissa.srw, mripard, tzimmermann, daniel.vetter, syzkaller-bugs,
	syzbot+2e93e6fb36e6fdc56574, Karol Herbst, Lyude Paul,
	Danilo Krummrich, nouveau

On Mon, Nov 20, 2023 at 10:41:18PM +0800, Edward Adam Davis wrote:
> [Syz Log]
> divide error: 0000 [#1] PREEMPT SMP KASAN
> CPU: 0 PID: 5068 Comm: syz-executor357 Not tainted 6.6.0-syzkaller-16039-gac347a0655db #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
> RIP: 0010:drm_mode_vrefresh drivers/gpu/drm/drm_modes.c:1303 [inline]
> RIP: 0010:drm_mode_debug_printmodeline+0x118/0x4e0 drivers/gpu/drm/drm_modes.c:60
> Code: 00 41 0f b7 07 66 83 f8 02 b9 01 00 00 00 0f 43 c8 0f b7 c1 0f af e8 44 89 f0 48 69 c8 e8 03 00 00 89 e8 d1 e8 48 01 c8 31 d2 <48> f7 f5 49 89 c6 eb 0c e8 fb 07 66 fc eb 05 e8 f4 07 66 fc 48 89
> RSP: 0018:ffffc9000391f8d0 EFLAGS: 00010246
> RAX: 000000000001f400 RBX: ffff888025045000 RCX: 000000000001f400
> RDX: 0000000000000000 RSI: 0000000000008000 RDI: ffff888025045018
> RBP: 0000000000000000 R08: ffffffff8528b9af R09: 0000000000000000
> R10: ffffc9000391f8a0 R11: fffff52000723f17 R12: 0000000000000080
> R13: dffffc0000000000 R14: 0000000000000080 R15: ffff888025045016
> FS:  0000555556932380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00000000005fdeb8 CR3: 000000007fcff000 CR4: 00000000003506f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
>  <TASK>
>  drm_mode_setcrtc+0x83b/0x1880 drivers/gpu/drm/drm_crtc.c:794
>  drm_ioctl_kernel+0x362/0x500 drivers/gpu/drm/drm_ioctl.c:792
>  drm_ioctl+0x636/0xb00 drivers/gpu/drm/drm_ioctl.c:895
>  vfs_ioctl fs/ioctl.c:51 [inline]
>  __do_sys_ioctl fs/ioctl.c:871 [inline]
>  __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:857
>  do_syscall_x64 arch/x86/entry/common.c:51 [inline]
>  do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
>  entry_SYSCALL_64_after_hwframe+0x63/0x6b
> 
> [Analysis]
> When calculating den in drm_mode_vrefresh(), if the vscan value is too large, 
> there is a probability of unsigned integer overflow.
> 
> [Fix]
> Before multiplying by vscan, first check if their product will overflow. 
> If overflow occurs, return 0 and exit the subsequent process.
> 
> Reported-and-tested-by: syzbot+2e93e6fb36e6fdc56574@syzkaller.appspotmail.com
> Fixes: ea40d7857d52 ("drm/vkms: fbdev emulation support")
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
> ---
>  drivers/gpu/drm/drm_modes.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletion(-)
> 
> diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
> index ac9a406250c5..60739d861da2 100644
> --- a/drivers/gpu/drm/drm_modes.c
> +++ b/drivers/gpu/drm/drm_modes.c
> @@ -36,6 +36,7 @@
>  #include <linux/list.h>
>  #include <linux/list_sort.h>
>  #include <linux/of.h>
> +#include <linux/overflow.h>
>  
>  #include <video/of_display_timing.h>
>  #include <video/of_videomode.h>
> @@ -1297,8 +1298,10 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
>  		num *= 2;
>  	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
>  		den *= 2;
> -	if (mode->vscan > 1)
> -		den *= mode->vscan;
> +	if (mode->vscan > 1) {
> +		if (unlikely(check_mul_overflow(den, mode->vscan, &den)))
> +			return 0;
> +	}

I can't see any driver that actually supports vscan>1. Only
nouveau has some code for it, but doesn't look like it does
anything sensible. All other drivers for sure should be
rejecting vscan>1 outright. Which driver is this?

Is there an actual usecase where nouveau needs this (and does
it even work?) or could we just rip out the whole thing and
reject vscan>1 globally?

>  
>  	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
>  }
> -- 
> 2.25.1

-- 
Ville Syrjälä
Intel

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [PATCH V2] drm/modes: Fix divide error in drm_mode_debug_printmodeline
  2023-11-20 15:12       ` [PATCH V2] " Ville Syrjälä
@ 2023-11-21  9:20         ` Jani Nikula
  0 siblings, 0 replies; 144+ messages in thread
From: Jani Nikula @ 2023-11-21  9:20 UTC (permalink / raw)
  To: Ville Syrjälä, Edward Adam Davis
  Cc: airlied, daniel.vetter, linux-kernel, dri-devel, melissa.srw,
	mripard, tzimmermann, daniel.vetter, syzkaller-bugs,
	syzbot+2e93e6fb36e6fdc56574, Karol Herbst, Lyude Paul,
	Danilo Krummrich, nouveau

On Mon, 20 Nov 2023, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Mon, Nov 20, 2023 at 10:41:18PM +0800, Edward Adam Davis wrote:
>> [Syz Log]
>> divide error: 0000 [#1] PREEMPT SMP KASAN
>> CPU: 0 PID: 5068 Comm: syz-executor357 Not tainted 6.6.0-syzkaller-16039-gac347a0655db #0
>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
>> RIP: 0010:drm_mode_vrefresh drivers/gpu/drm/drm_modes.c:1303 [inline]
>> RIP: 0010:drm_mode_debug_printmodeline+0x118/0x4e0 drivers/gpu/drm/drm_modes.c:60
>> Code: 00 41 0f b7 07 66 83 f8 02 b9 01 00 00 00 0f 43 c8 0f b7 c1 0f af e8 44 89 f0 48 69 c8 e8 03 00 00 89 e8 d1 e8 48 01 c8 31 d2 <48> f7 f5 49 89 c6 eb 0c e8 fb 07 66 fc eb 05 e8 f4 07 66 fc 48 89
>> RSP: 0018:ffffc9000391f8d0 EFLAGS: 00010246
>> RAX: 000000000001f400 RBX: ffff888025045000 RCX: 000000000001f400
>> RDX: 0000000000000000 RSI: 0000000000008000 RDI: ffff888025045018
>> RBP: 0000000000000000 R08: ffffffff8528b9af R09: 0000000000000000
>> R10: ffffc9000391f8a0 R11: fffff52000723f17 R12: 0000000000000080
>> R13: dffffc0000000000 R14: 0000000000000080 R15: ffff888025045016
>> FS:  0000555556932380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
>> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> CR2: 00000000005fdeb8 CR3: 000000007fcff000 CR4: 00000000003506f0
>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>> Call Trace:
>>  <TASK>
>>  drm_mode_setcrtc+0x83b/0x1880 drivers/gpu/drm/drm_crtc.c:794
>>  drm_ioctl_kernel+0x362/0x500 drivers/gpu/drm/drm_ioctl.c:792
>>  drm_ioctl+0x636/0xb00 drivers/gpu/drm/drm_ioctl.c:895
>>  vfs_ioctl fs/ioctl.c:51 [inline]
>>  __do_sys_ioctl fs/ioctl.c:871 [inline]
>>  __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:857
>>  do_syscall_x64 arch/x86/entry/common.c:51 [inline]
>>  do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82
>>  entry_SYSCALL_64_after_hwframe+0x63/0x6b
>> 
>> [Analysis]
>> When calculating den in drm_mode_vrefresh(), if the vscan value is too large, 
>> there is a probability of unsigned integer overflow.
>> 
>> [Fix]
>> Before multiplying by vscan, first check if their product will overflow. 
>> If overflow occurs, return 0 and exit the subsequent process.
>> 
>> Reported-and-tested-by: syzbot+2e93e6fb36e6fdc56574@syzkaller.appspotmail.com
>> Fixes: ea40d7857d52 ("drm/vkms: fbdev emulation support")
>> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
>> ---
>>  drivers/gpu/drm/drm_modes.c | 7 +++++--
>>  1 file changed, 5 insertions(+), 2 deletion(-)
>> 
>> diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c
>> index ac9a406250c5..60739d861da2 100644
>> --- a/drivers/gpu/drm/drm_modes.c
>> +++ b/drivers/gpu/drm/drm_modes.c
>> @@ -36,6 +36,7 @@
>>  #include <linux/list.h>
>>  #include <linux/list_sort.h>
>>  #include <linux/of.h>
>> +#include <linux/overflow.h>
>>  
>>  #include <video/of_display_timing.h>
>>  #include <video/of_videomode.h>
>> @@ -1297,8 +1298,10 @@ int drm_mode_vrefresh(const struct drm_display_mode *mode)
>>  		num *= 2;
>>  	if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
>>  		den *= 2;
>> -	if (mode->vscan > 1)
>> -		den *= mode->vscan;
>> +	if (mode->vscan > 1) {
>> +		if (unlikely(check_mul_overflow(den, mode->vscan, &den)))
>> +			return 0;
>> +	}
>
> I can't see any driver that actually supports vscan>1. Only
> nouveau has some code for it, but doesn't look like it does
> anything sensible. All other drivers for sure should be
> rejecting vscan>1 outright. Which driver is this?
>
> Is there an actual usecase where nouveau needs this (and does
> it even work?) or could we just rip out the whole thing and
> reject vscan>1 globally?

I thought the whole thing seemed familiar [1].

BR,
Jani.



[1] https://lore.kernel.org/r/20230802174746.2256-1-astrajoan@yahoo.com


>
>>  
>>  	return DIV_ROUND_CLOSEST_ULL(mul_u32_u32(num, 1000), den);
>>  }
>> -- 
>> 2.25.1

-- 
Jani Nikula, Intel

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2018-11-24 19:40 WARNING in csum_and_copy_to_iter syzbot
@ 2023-11-24 10:30 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2023-11-24 10:30 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

The issue has not been happening for >1800 days.

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
       [not found] <mailman.217.1706634262.2961.pvrusb2@isely.net>
@ 2024-02-15 16:26 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-02-15 16:26 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: mazin@getstate.dev

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-01-12 20:14 [syzbot] upstream build error (21) syzbot
@ 2024-06-20  8:00 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-06-20  8:00 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2023-06-05  3:53 [syzbot] [ext4?] WARNING: locking bug in ext4_move_extents syzbot
@ 2024-07-03  7:48 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-07-03  7:48 UTC (permalink / raw)
  To: linux-kernel

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: 
Author: bottaawesome633@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2022-10-17  7:43 [syzbot] possible deadlock in attr_data_get_block syzbot
@ 2024-07-17  8:19 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-07-17  8:19 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: almaz.alexandrovich@paragon-software.com

#syz test: https://github.com/Paragon-Software-Group/linux-ntfs3.git 
d57431c6f511bf020e474026d9f3123d7bfbea8c





^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2021-02-26 14:48 general protection fault in try_to_wake_up (2) syzbot
@ 2024-07-25 16:29 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-07-25 16:29 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: axboe@kernel.dk

#syz invalid

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-01-05 17:32 [syzbot] [net?] memory leak in ___neigh_create (2) syzbot
@ 2024-09-05 11:54 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-09-05 11:54 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-08-27  2:12 [syzbot] [sound?] WARNING in snd_pcm_open syzbot
@ 2024-09-06 10:33 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-09-06 10:33 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2020-08-04 15:46 KASAN: use-after-free Read in __sco_sock_close syzbot
@ 2024-09-06 10:35 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-09-06 10:35 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

The reproducer now hits

WARNING: CPU: 0 PID: 5640 at net/bluetooth/hci_conn.c:565
hci_conn_timeout+0xfb/0x290 net/bluetooth/hci_conn.c:565

for which we have a separate bug.

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2022-07-12 12:03 [syzbot] inconsistent lock state in find_vmap_area syzbot
@ 2024-09-06 10:36 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-09-06 10:36 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

Repro now triggers a different kind of problem

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2023-11-16 11:09 [syzbot] [kernel?] inconsistent lock state in __lock_task_sighand syzbot
@ 2024-09-06 10:37 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-09-06 10:37 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2023-10-16  7:38 [syzbot] [kernel?] KASAN: slab-use-after-free Read in reweight_entity syzbot
@ 2024-09-06 10:38 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-09-06 10:38 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

Repro triggers a different kind of an issue

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2022-09-25 11:18 [syzbot] WARNING in __change_page_attr_set_clr syzbot
@ 2024-09-06 10:39 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-09-06 10:39 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

Repro triggers a different problem

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2020-11-21  1:55 INFO: task can't die in shrink_inactive_list (2) syzbot
@ 2024-09-06 10:39 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-09-06 10:39 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2020-08-08 21:27 KASAN: use-after-free Read in __queue_work (3) syzbot
@ 2024-09-06 10:40 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-09-06 10:40 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

Repro triggers a different kind of problem

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-03 17:42 [syzbot] [bcachefs?] possible deadlock in bch2_replicas_entry_validate syzbot
@ 2024-10-16  6:42 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-10-16  6:42 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Fix lockdep splat in bch2_accounting_read

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-21  6:44 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in bch2_alloc_to_text syzbot
@ 2024-10-26  0:47 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-10-26  0:47 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: fix shift oob in alloc_lru_idx_fragmentation

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-23 14:27 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in validate_sb_layout syzbot
@ 2024-10-26  0:49 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-10-26  0:49 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Fix invalid shift in validate_sb_layout()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2021-02-01 10:07 BUG: Bad page state (8) syzbot
@ 2024-10-28 14:11 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-10-28 14:11 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-21  4:31 [syzbot] [bcachefs?] kernel BUG in __bch2_trans_commit syzbot
@ 2024-11-08  0:18 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-08  0:18 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: -o norecovery now bails out of recovery earlier

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-25  6:49 [syzbot] [bcachefs?] kernel BUG in __bch2_bkey_cmp_packed_format_checked syzbot
@ 2024-11-08  0:34 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-08  0:34 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Ancient versions with bad bkey_formats are no longer supported

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-27  3:54 [syzbot] [bcachefs?] kernel BUG in bch2_inconsistent_error syzbot
@ 2024-11-08  0:48 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-08  0:48 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Change OPT_STR max to be 1 less than the size of choices array

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-09-28  2:13 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_write_buffer_exit syzbot
@ 2024-11-08  3:04 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-08  3:04 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: bch2_btree_write_buffer_flush_going_ro()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-25  6:49 [syzbot] [bcachefs?] kernel BUG in bch2_trans_node_iter_init syzbot
@ 2024-11-08  3:21 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-08  3:21 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix missing validation for bch_backpointer.level

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-25  6:48 [syzbot] [bcachefs?] kernel BUG in bch2_journal_res_get (2) syzbot
@ 2024-11-08  3:28 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-08  3:28 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: bch2_btree_write_buffer_flush_going_ro()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-21 13:07 [syzbot] [bcachefs?] kernel BUG in bch2_dev_btree_bitmap_mark syzbot
@ 2024-11-08  4:25 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-08  4:25 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix bch_member.btree_bitmap_shift validation

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-30 16:39 [syzbot] [bcachefs?] kernel BUG in __bkey_unpack_pos syzbot
@ 2024-11-08  5:02 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-08  5:02 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix validate_bset() repair path

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-27  1:10 [syzbot] [bcachefs?] kernel BUG in bch2_bkey_pack_pos_lossy syzbot
@ 2024-11-08  5:11 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-08  5:11 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix validate_bset() repair path

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-09 15:43 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_hash_insert syzbot
@ 2024-11-11  3:13 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-11  3:13 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix assertion pop in topology repair

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-23 11:21 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_level_init (2) syzbot
@ 2024-11-11  3:14 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-11  3:14 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix missing validation for bch_backpointer.level

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-24 17:47 [syzbot] [bcachefs?] kernel BUG in bch2_run_recovery_pass syzbot
@ 2024-11-11  4:31 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-11  4:31 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Allow for unknown key types in backpointers fsck

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-18  7:37 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_cache_exit syzbot
@ 2024-11-11  4:46 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-11  4:46 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: bch2_btree_write_buffer_flush_going_ro()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-07-30  1:14 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in journal_entry_dev_usage_to_text syzbot
@ 2024-11-11 21:03 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-11 21:03 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix journal_entry_dev_usage_to_text() overrun

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-23  4:12 [syzbot] [bcachefs?] kernel BUG in bch2_ptr_swab syzbot
@ 2024-11-11 21:16 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-11 21:16 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix assertion pop in bch2_ptr_swab()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2020-10-13 17:02 WARNING in drop_nlink (2) syzbot
@ 2024-11-20 15:35 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-20 15:35 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

There will be no such crash title under the new report extraction rules

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-22 18:44 [syzbot] [bcachefs?] kernel BUG in bch2_btree_pos_to_text (2) syzbot
@ 2024-11-25  3:59 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-25  3:59 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix btree node scan when unknown btree IDs are present

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-03  8:10 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_write syzbot
@ 2024-11-25  6:52 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-25  6:52 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix dup/misordered check in btree node read

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-22 15:15 [syzbot] [bcachefs?] kernel BUG in bch2_btree_root_read syzbot
@ 2024-11-25  6:53 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-25  6:53 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Kill bch2_bucket_alloc_new_fs()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-18 21:41 [syzbot] [bcachefs?] kernel BUG in bch2_bucket_alloc_trans (3) syzbot
@ 2024-11-25  6:54 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-25  6:54 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Kill bch2_bucket_alloc_new_fs()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-06-14 12:16 [syzbot] [crypto?] [bcachefs?] BUG: unable to handle kernel paging request in crypto_skcipher_encrypt syzbot
@ 2024-11-25  7:19 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-25  7:19 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Don't try to en/decrypt when encryption not available

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-25  6:48 [syzbot] [bcachefs?] general protection fault in bch2_btree_path_traverse_one syzbot
@ 2024-11-27  8:09 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-27  8:09 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Ignore empty btree root journal entries

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-25  3:10 [syzbot] [bcachefs?] kernel BUG in __bch2_journal_pin_put syzbot
@ 2024-11-28  3:00 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28  3:00 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Guard against journal seq overflow

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-21 12:40 [syzbot] [bcachefs?] kernel BUG in bch2_btree_node_lock_write syzbot
@ 2024-11-28  3:12 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28  3:12 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Issue a transaction restart after commit in repair

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-28 15:49 [syzbot] [bcachefs?] kernel BUG in bch2_btree_write_buffer_flush_locked syzbot
@ 2024-11-28  3:21 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28  3:21 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Guard against journal seq overflow

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-25 13:28 [syzbot] [bcachefs?] kernel BUG in bch2_journal_pin_set syzbot
@ 2024-11-28  3:23 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28  3:23 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Guard against journal seq overflow

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-06 13:24 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_traverse_one syzbot
@ 2024-11-28  3:27 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28  3:27 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix btree node scan when unknown btree IDs are present

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-25 13:28 [syzbot] [bcachefs?] BUG: corrupted list in bch2_btree_and_journal_iter_exit syzbot
@ 2024-11-28 20:12 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28 20:12 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix journal_iter list corruption

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-28  9:49 [syzbot] [bcachefs?] kernel BUG in bch2_get_scanned_nodes syzbot
@ 2024-11-28 20:31 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28 20:31 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: struct bkey_validate_context

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-07-10 20:55 [syzbot] [bcachefs?] kernel BUG in bch2_journal_noflush_seq syzbot
@ 2024-11-28 22:12 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28 22:12 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Check for bucket journal sequence numbers from the future

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-09-18  7:28 [syzbot] [bcachefs?] WARNING in bch2_journal_flush_seq_async syzbot
@ 2024-11-28 22:50 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28 22:50 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Check for inode journal seq in the future

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-07-17 13:39 [syzbot] [bcachefs?] general protection fault in bch2_checksum syzbot
@ 2024-11-28 22:59 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28 22:59 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: cryptographic MACs on superblock are not (yet?) supported

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-10-23 18:30 [syzbot] [bcachefs?] possible deadlock in __bch2_trans_relock syzbot
@ 2024-11-28 23:06 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-28 23:06 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: bch2_trans_relock() is trylock for lockdep

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-08 15:57 [syzbot] [bcachefs?] kernel BUG in bch2_rechecksum_bio syzbot
@ 2024-11-29  0:32 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-29  0:32 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Check for extent crc uncompressed/compressed size mismatch

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-12  3:25 [syzbot] [bcachefs?] possible deadlock in bch2_alloc_sectors_start_trans syzbot
@ 2024-11-29  0:34 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-29  0:34 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Don't recurse in check_discard_freespace_key

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-25 13:05 [syzbot] [bcachefs?] kernel BUG in bch2_evacuate_bucket syzbot
@ 2024-11-29  0:39 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-11-29  0:39 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Kill bch2_get_next_backpointer()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-07-24  8:59 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_remove_adv_monitor_sync syzbot
@ 2024-12-05  1:58 ` syzbot
  2024-12-23 22:19 ` [syzbot] syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2024-12-05  1:58 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: mazin@getstate.dev

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-22 14:42 [syzbot] [netfilter?] KMSAN: uninit-value in ip6table_mangle_hook (3) syzbot
@ 2024-12-14 22:16 ` syzbot
  2024-12-14 22:21 ` [syzbot] syzbot
  2024-12-15  2:34 ` [syzbot] syzbot
  2 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-12-14 22:16 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: mazin@getstate.dev

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-22 14:42 [syzbot] [netfilter?] KMSAN: uninit-value in ip6table_mangle_hook (3) syzbot
  2024-12-14 22:16 ` [syzbot] syzbot
@ 2024-12-14 22:21 ` syzbot
  2024-12-15  2:34 ` [syzbot] syzbot
  2 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-12-14 22:21 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: mazin@getstate.dev

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-22 14:42 [syzbot] [netfilter?] KMSAN: uninit-value in ip6table_mangle_hook (3) syzbot
  2024-12-14 22:16 ` [syzbot] syzbot
  2024-12-14 22:21 ` [syzbot] syzbot
@ 2024-12-15  2:34 ` syzbot
  2 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-12-15  2:34 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: mazin@getstate.dev

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-07-24  8:59 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_remove_adv_monitor_sync syzbot
  2024-12-05  1:58 ` [syzbot] syzbot
@ 2024-12-23 22:19 ` syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2024-12-23 22:19 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: mazin@getstate.dev

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-24  6:38 [syzbot] [input?] KASAN: null-ptr-deref Write in input_ff_create syzbot
@ 2024-12-25 16:44 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-12-25 16:44 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-25  2:26 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in force_devcd_write syzbot
@ 2024-12-26  3:43 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2024-12-26  3:43 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: mazin@getstate.dev

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-01-02 14:45 [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in f2fs_getxattr syzbot
@ 2025-01-07 22:19 ` syzbot
  2025-01-08 14:13 ` [syzbot] syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-01-07 22:19 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-01-02 14:45 [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in f2fs_getxattr syzbot
  2025-01-07 22:19 ` [syzbot] syzbot
@ 2025-01-08 14:13 ` syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-01-08 14:13 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2022-12-21  8:15 [syzbot] possible deadlock in page_cache_ra_unbounded syzbot
@ 2025-01-08 16:11 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-01-08 16:11 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz set subsystems: mm, fs

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-01-11  0:40 [syzbot] [usb?] general protection fault in qt2_read_bulk_callback syzbot
@ 2025-01-11 17:19 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-01-11 17:19 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-01-12  6:45 [syzbot] [iommu?] UBSAN: shift-out-of-bounds in iova_bitmap_alloc syzbot
@ 2025-01-12 11:58 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-01-12 11:58 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-01-17  6:14 [syzbot] [usb?] general protection fault in status_show syzbot
@ 2025-01-17 15:41 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-01-17 15:41 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot] [dri?] divide error in drm_mode_debug_printmodeline
  2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
                   ` (11 preceding siblings ...)
  2023-11-20 13:30 ` syzbot
@ 2025-01-18 18:25 ` syzbot
  12 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-01-18 18:25 UTC (permalink / raw)
  To: airlied, airlied, dakr, daniel.vetter, daniel.vetter, daniel,
	dri-devel, eadavis, jani.nikula, jani.nikula, kherbst,
	linux-kernel, lizhi.xu, lyude, maarten.lankhorst, mazinalhaddad05,
	melissa.srw, mripard, nouveau, simona, syzkaller-bugs,
	tzimmermann, ville.syrjala

syzbot suspects this issue was fixed by commit:

commit 9398332f23fab10c5ec57c168b44e72997d6318e
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
Date:   Fri Nov 29 04:26:28 2024 +0000

    drm/modes: Avoid divide by zero harder in drm_mode_vrefresh()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11797a18580000
start commit:   ac347a0655db Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=88e7ba51eecd9cd6
dashboard link: https://syzkaller.appspot.com/bug?extid=2e93e6fb36e6fdc56574
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11252f97680000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10fd2498e80000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: drm/modes: Avoid divide by zero harder in drm_mode_vrefresh()

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-27  0:00 [syzbot] upstream build error (22) syzbot
@ 2025-02-03 12:55 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-03 12:55 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

All the previous reasons for build breakages are no longer relevant.

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-09  5:48 [syzbot] [isofs?] KMSAN: uninit-value in isofs_readdir syzbot
@ 2025-02-09 23:50 ` syzbot
  2025-02-11  1:00 ` [syzbot] syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-09 23:50 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-09  5:48 [syzbot] [isofs?] KMSAN: uninit-value in isofs_readdir syzbot
  2025-02-09 23:50 ` [syzbot] syzbot
@ 2025-02-11  1:00 ` syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-11  1:00 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-12 10:57 [syzbot] [jfs?] KASAN: slab-out-of-bounds Read in ea_get (4) syzbot
@ 2025-02-12 22:56 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-12 22:56 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-12 13:41 [syzbot] [modules?] KMSAN: uninit-value in __request_module (6) syzbot
@ 2025-02-13 14:21 ` syzbot
  2025-02-13 18:22 ` [syzbot] syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-13 14:21 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: purvayeshi550@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-12 13:41 [syzbot] [modules?] KMSAN: uninit-value in __request_module (6) syzbot
  2025-02-13 14:21 ` [syzbot] syzbot
@ 2025-02-13 18:22 ` syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-13 18:22 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: purvayeshi550@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
@ 2025-02-15  7:58 ` syzbot
  2025-02-15 12:33 ` [syzbot] syzbot
                   ` (6 subsequent siblings)
  7 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-15  7:58 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: purvayeshi550@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
  2025-02-15  7:58 ` [syzbot] syzbot
@ 2025-02-15 12:33 ` syzbot
  2025-02-15 14:31 ` [syzbot] syzbot
                   ` (5 subsequent siblings)
  7 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-15 12:33 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: purvayeshi550@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
  2025-02-15  7:58 ` [syzbot] syzbot
  2025-02-15 12:33 ` [syzbot] syzbot
@ 2025-02-15 14:31 ` syzbot
  2025-02-15 18:42 ` [syzbot] syzbot
                   ` (4 subsequent siblings)
  7 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-15 14:31 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: purvayeshi550@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
                   ` (2 preceding siblings ...)
  2025-02-15 14:31 ` [syzbot] syzbot
@ 2025-02-15 18:42 ` syzbot
  2025-02-15 19:35 ` [syzbot] syzbot
                   ` (3 subsequent siblings)
  7 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-15 18:42 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: purvayeshi550@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
                   ` (3 preceding siblings ...)
  2025-02-15 18:42 ` [syzbot] syzbot
@ 2025-02-15 19:35 ` syzbot
  2025-04-07 14:06 ` [syzbot] Arnaud Lecomte
                   ` (2 subsequent siblings)
  7 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-15 19:35 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: purvayeshi550@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-17 11:55 [syzbot] [can?] WARNING in ucan_probe syzbot
@ 2025-02-17 17:59 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-17 17:59 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test


^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-17 11:55 [syzbot] [usb?] KMSAN: uninit-value in mii_nway_restart (2) syzbot
@ 2025-02-17 20:59 ` syzbot
  2025-04-11 12:15 ` [syzbot] syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-02-17 20:59 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test


^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-03-09  4:20 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_extent_crc_append (2) syzbot
@ 2025-04-01  3:55 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  3:55 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Fix kmsan warnings in bch2_extent_crc_pack()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-04 15:33 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_ptr_v2_validate syzbot
@ 2025-04-01  3:56 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  3:56 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-01-29  9:17 [syzbot] [bcachefs?] KMSAN: uninit-value in btree_interior_update_work syzbot
@ 2025-04-01  3:57 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  3:57 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix  bcachefs: Fix a KMSAN splat in btree_update_nodes_written()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-01-03  1:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_trans_start_alloc_update_noupdate syzbot
@ 2025-04-01  3:58 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  3:58 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-01-01 20:55 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_inode_unpack (2) syzbot
@ 2025-04-01  3:58 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  3:58 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-01-11 13:37 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_readdir (2) syzbot
@ 2025-04-01  3:59 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  3:59 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-01  9:40 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_get syzbot
@ 2025-04-01  3:59 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  3:59 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-17  8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_v4_validate (2) syzbot
@ 2025-04-01  4:00 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:00 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-27 18:59 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_cmp_packed_inlined (2) syzbot
@ 2025-04-01  4:01 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:01 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-01  8:34 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_ptrs_validate syzbot
@ 2025-04-01  4:02 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:02 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-29 16:59 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_val_validate syzbot
@ 2025-04-01  4:02 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:02 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-24 14:42 [syzbot] [bcachefs?] KMSAN: uninit-value in __bch2_bkey_cmp_left_packed syzbot
@ 2025-04-01  4:02 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:02 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-13 19:13 [syzbot] [bcachefs?] KMSAN: uninit-value in __build_ro_aux_tree syzbot
@ 2025-04-01  4:03 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:03 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-04 17:36 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dev_freespace_init syzbot
@ 2025-04-01  4:03 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:03 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-19 10:14 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dirent_rename (2) syzbot
@ 2025-04-01  4:04 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:04 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-30 19:55 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dirent_validate syzbot
@ 2025-04-01  4:04 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:04 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-06 13:58 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bucket_alloc_early syzbot
@ 2025-04-01  4:05 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:05 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-13  7:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_xattr_validate syzbot
@ 2025-04-01  4:06 ` syzbot
  2025-04-01  4:07 ` [syzbot] syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:06 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-15  8:10 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_checksum_update (2) syzbot
@ 2025-04-01  4:06 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:06 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-17  8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_iter_init (2) syzbot
@ 2025-04-01  4:07 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:07 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-12-13  7:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_xattr_validate syzbot
  2025-04-01  4:06 ` [syzbot] syzbot
@ 2025-04-01  4:07 ` syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:07 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-19  7:33 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_inode_v3_validate syzbot
@ 2025-04-01  4:08 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:08 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-26  0:00 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_trans_start_alloc_update syzbot
@ 2025-04-01  4:08 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:08 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-22 18:44 [syzbot] [bcachefs?] KMSAN: uninit-value in rw_aux_tree_set (2) syzbot
@ 2025-04-01  4:09 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:09 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-11-11  0:28 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_check_topology syzbot
@ 2025-04-01  4:10 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:10 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Disable asm memcpys when kmsan enabled

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-03-31 14:06 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_copygc (2) syzbot
@ 2025-04-01  4:10 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01  4:10 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix bcachefs: Eliminate padding in move_bucket_key

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-03-31  2:14 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in __kfifo_alloc syzbot
@ 2025-04-01 10:18 ` syzbot
  2025-04-01 10:24 ` [syzbot] syzbot
  2025-04-01 11:04 ` [syzbot] syzbot
  2 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01 10:18 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-03-31  2:14 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in __kfifo_alloc syzbot
  2025-04-01 10:18 ` [syzbot] syzbot
@ 2025-04-01 10:24 ` syzbot
  2025-04-01 11:04 ` [syzbot] syzbot
  2 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01 10:24 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-03-31  2:14 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in __kfifo_alloc syzbot
  2025-04-01 10:18 ` [syzbot] syzbot
  2025-04-01 10:24 ` [syzbot] syzbot
@ 2025-04-01 11:04 ` syzbot
  2 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-01 11:04 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-03-30 10:15 [syzbot] [pci?] upstream test error: general protection fault in msix_prepare_msi_desc syzbot
@ 2025-04-03  7:06 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-03  7:06 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-03-30 16:49 [syzbot] [pci?] upstream test error: BUG: unable to handle kernel NULL pointer dereference in msix_prepare_msi_desc syzbot
@ 2025-04-03  7:06 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-03  7:06 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
                   ` (4 preceding siblings ...)
  2025-02-15 19:35 ` [syzbot] syzbot
@ 2025-04-07 14:06 ` Arnaud Lecomte
  2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
  2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
  7 siblings, 0 replies; 144+ messages in thread
From: Arnaud Lecomte @ 2025-04-07 14:06 UTC (permalink / raw)
  To: syzbot+29fc8991b0ecb186cf40
  Cc: andrew+netdev, davem, edumazet, kuba, linux-kernel, linux-ppp,
	netdev, pabeni, syzkaller-bugs

#syz test: https://github.com/ArnaudLcm/linux bounds-checking-txmung

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
                   ` (5 preceding siblings ...)
  2025-04-07 14:06 ` [syzbot] Arnaud Lecomte
@ 2025-04-07 14:17 ` Arnaud Lecomte
  2025-04-07 14:17   ` [syzbot] syzbot
  2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
  7 siblings, 1 reply; 144+ messages in thread
From: Arnaud Lecomte @ 2025-04-07 14:17 UTC (permalink / raw)
  To: syzbot+29fc8991b0ecb186cf40
  Cc: andrew+netdev, davem, edumazet, kuba, linux-kernel, linux-ppp,
	netdev, pabeni, syzkaller-bugs

Author: contact@arnaud-lcm.com

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
index 644e99fc3623..520d895acc60 100644
--- a/drivers/net/ppp/ppp_synctty.c
+++ b/drivers/net/ppp/ppp_synctty.c
@@ -506,6 +506,11 @@ ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)
 	unsigned char *data;
 	int islcp;
 
+	/* Ensure we can safely access protocol field and LCP code */
+	if (!skb || !pskb_may_pull(skb, 3)) {
+		kfree_skb(skb);
+		return NULL;
+	}
 	data  = skb->data;
 	proto = get_unaligned_be16(data);

^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
@ 2025-04-07 14:17   ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-07 14:17 UTC (permalink / raw)
  To: contact
  Cc: andrew, contact, davem, edumazet, kuba, linux-kernel, linux-ppp,
	netdev, pabeni, syzkaller-bugs

> Author: contact@arnaud-lcm.com
>
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

want either no args or 2 args (repo, branch), got 5

>
> diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
> index 644e99fc3623..520d895acc60 100644
> --- a/drivers/net/ppp/ppp_synctty.c
> +++ b/drivers/net/ppp/ppp_synctty.c
> @@ -506,6 +506,11 @@ ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)
>  	unsigned char *data;
>  	int islcp;
>  
> +	/* Ensure we can safely access protocol field and LCP code */
> +	if (!skb || !pskb_may_pull(skb, 3)) {
> +		kfree_skb(skb);
> +		return NULL;
> +	}
>  	data  = skb->data;
>  	proto = get_unaligned_be16(data);

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
                   ` (6 preceding siblings ...)
  2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
@ 2025-04-07 14:17 ` Arnaud Lecomte
  7 siblings, 0 replies; 144+ messages in thread
From: Arnaud Lecomte @ 2025-04-07 14:17 UTC (permalink / raw)
  To: syzbot+29fc8991b0ecb186cf40
  Cc: andrew+netdev, davem, edumazet, kuba, linux-kernel, linux-ppp,
	netdev, pabeni, syzkaller-bugs

Author: contact@arnaud-lcm.com

#syz test

diff --git a/drivers/net/ppp/ppp_synctty.c b/drivers/net/ppp/ppp_synctty.c
index 644e99fc3623..520d895acc60 100644
--- a/drivers/net/ppp/ppp_synctty.c
+++ b/drivers/net/ppp/ppp_synctty.c
@@ -506,6 +506,11 @@ ppp_sync_txmunge(struct syncppp *ap, struct sk_buff *skb)
 	unsigned char *data;
 	int islcp;
 
+	/* Ensure we can safely access protocol field and LCP code */
+	if (!skb || !pskb_may_pull(skb, 3)) {
+		kfree_skb(skb);
+		return NULL;
+	}
 	data  = skb->data;
 	proto = get_unaligned_be16(data);

^ permalink raw reply related	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-17 11:55 [syzbot] [usb?] KMSAN: uninit-value in mii_nway_restart (2) syzbot
  2025-02-17 20:59 ` [syzbot] syzbot
@ 2025-04-11 12:15 ` syzbot
  1 sibling, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-11 12:15 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: qasdev00@gmail.com

#syz test

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-02-23  6:02 [syzbot] linux-next build error (20) syzbot
@ 2025-04-14 14:48 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-14 14:48 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: nogikh@google.com

The bug was fixed with a different commit than the recorded [PATCH] discussion.
Close it so that it may be reopened the next time we face a linux next
build problem.

#syz invalid

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-04-08 11:53 [syzbot] [bcachefs?] WARNING in bch2_dev_free syzbot
@ 2025-04-18  0:37 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-04-18  0:37 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Prevent granting write refs when filesystem is read-only

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-05-26 10:41 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v2_to_text syzbot
@ 2025-06-08 15:33 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-06-08 15:33 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Don't trust sb->nr_devices in members_to_text()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-05-26  8:50 [syzbot] [bcachefs?] WARNING in rhashtable_init_noprof syzbot
@ 2025-06-08 15:41 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-06-08 15:41 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Don't put rhashtable on stack

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-04-28 17:04 [syzbot] [bcachefs?] UBSAN: array-index-out-of-bounds in bch2_sb_downgrade_update syzbot
@ 2025-06-08 16:01 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-06-08 16:01 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix downgrade_table_extra()

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2024-07-13 22:54 [syzbot] [bpf?] [trace?] possible deadlock in console_flush_all (3) syzbot
@ 2025-06-19 20:48 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-06-19 20:48 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Fix possible console lock involved deadlock

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-06-12  7:52 [syzbot] [bcachefs?] WARNING in __init_work (2) syzbot
@ 2025-06-19 20:54 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-06-19 20:54 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Don't put rhashtable on stack

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-05-31 15:09 [syzbot] [bcachefs?] WARNING in lookup_object_or_alloc syzbot
@ 2025-06-19 20:54 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-06-19 20:54 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Don't put rhashtable on stack

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-06-08  5:52 [syzbot] [bcachefs?] kernel BUG in vfs_get_tree (2) syzbot
@ 2025-06-19 20:57 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-06-19 20:57 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Call bch2_fs_start before getting vfs superblock

^ permalink raw reply	[flat|nested] 144+ messages in thread

* Re: [syzbot]
  2025-06-10 19:15 [syzbot] [bcachefs?] divide error in bch2_sb_members_v2_to_text syzbot
@ 2025-06-19 21:00 ` syzbot
  0 siblings, 0 replies; 144+ messages in thread
From: syzbot @ 2025-06-19 21:00 UTC (permalink / raw)
  To: linux-kernel, syzkaller-bugs

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: 
Author: kent.overstreet@linux.dev

#syz fix: bcachefs: Don't trust sb->nr_devices in members_to_text()

^ permalink raw reply	[flat|nested] 144+ messages in thread

end of thread, other threads:[~2025-06-19 21:00 UTC | newest]

Thread overview: 144+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-11-15  9:34 [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
2023-11-16  0:52 ` [syzbot] [PATCH] test " syzbot
2023-11-16  2:33 ` [syzbot] syzbot
2023-11-16  3:29 ` [syzbot] syzbot
2023-11-18  3:42 ` [syzbot] [PATCH] Test divide err in drm syzbot
2023-11-18  6:44 ` syzbot
2023-11-18 10:29 ` syzbot
2023-11-18 11:59 ` syzbot
2023-11-19  1:31 ` syzbot
     [not found] ` <tencent_F6C990AEE12ED34C8467CBC6FBD2F4467F06@qq.com>
2023-11-20 11:31   ` [PATCH] drm/modes: Fix divide error in drm_mode_debug_printmodeline Jani Nikula
     [not found]     ` <tencent_DCCE6C78766FE82D816F9C94F0EAC2ED260A@qq.com>
2023-11-20 15:12       ` [PATCH V2] " Ville Syrjälä
2023-11-21  9:20         ` Jani Nikula
2023-11-20 12:00 ` [syzbot] [PATCH] Test divide err in drm syzbot
2023-11-20 12:22 ` syzbot
2023-11-20 13:30 ` syzbot
2025-01-18 18:25 ` [syzbot] [dri?] divide error in drm_mode_debug_printmodeline syzbot
  -- strict thread matches above, loose matches on Subject: below --
2025-06-12  7:52 [syzbot] [bcachefs?] WARNING in __init_work (2) syzbot
2025-06-19 20:54 ` [syzbot] syzbot
2025-06-10 19:15 [syzbot] [bcachefs?] divide error in bch2_sb_members_v2_to_text syzbot
2025-06-19 21:00 ` [syzbot] syzbot
2025-06-08  5:52 [syzbot] [bcachefs?] kernel BUG in vfs_get_tree (2) syzbot
2025-06-19 20:57 ` [syzbot] syzbot
2025-05-31 15:09 [syzbot] [bcachefs?] WARNING in lookup_object_or_alloc syzbot
2025-06-19 20:54 ` [syzbot] syzbot
2025-05-26 10:41 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v2_to_text syzbot
2025-06-08 15:33 ` [syzbot] syzbot
2025-05-26  8:50 [syzbot] [bcachefs?] WARNING in rhashtable_init_noprof syzbot
2025-06-08 15:41 ` [syzbot] syzbot
2025-04-28 17:04 [syzbot] [bcachefs?] UBSAN: array-index-out-of-bounds in bch2_sb_downgrade_update syzbot
2025-06-08 16:01 ` [syzbot] syzbot
2025-04-08 11:53 [syzbot] [bcachefs?] WARNING in bch2_dev_free syzbot
2025-04-18  0:37 ` [syzbot] syzbot
2025-03-31 14:06 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_copygc (2) syzbot
2025-04-01  4:10 ` [syzbot] syzbot
2025-03-31  2:14 [syzbot] [input?] [usb?] UBSAN: shift-out-of-bounds in __kfifo_alloc syzbot
2025-04-01 10:18 ` [syzbot] syzbot
2025-04-01 10:24 ` [syzbot] syzbot
2025-04-01 11:04 ` [syzbot] syzbot
2025-03-30 16:49 [syzbot] [pci?] upstream test error: BUG: unable to handle kernel NULL pointer dereference in msix_prepare_msi_desc syzbot
2025-04-03  7:06 ` [syzbot] syzbot
2025-03-30 10:15 [syzbot] [pci?] upstream test error: general protection fault in msix_prepare_msi_desc syzbot
2025-04-03  7:06 ` [syzbot] syzbot
2025-03-09  4:20 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_extent_crc_append (2) syzbot
2025-04-01  3:55 ` [syzbot] syzbot
2025-02-23  6:02 [syzbot] linux-next build error (20) syzbot
2025-04-14 14:48 ` [syzbot] syzbot
2025-02-17 11:55 [syzbot] [can?] WARNING in ucan_probe syzbot
2025-02-17 17:59 ` [syzbot] syzbot
2025-02-17 11:55 [syzbot] [usb?] KMSAN: uninit-value in mii_nway_restart (2) syzbot
2025-02-17 20:59 ` [syzbot] syzbot
2025-04-11 12:15 ` [syzbot] syzbot
2025-02-13 18:25 [syzbot] [ppp?] KMSAN: uninit-value in ppp_sync_send (2) syzbot
2025-02-15  7:58 ` [syzbot] syzbot
2025-02-15 12:33 ` [syzbot] syzbot
2025-02-15 14:31 ` [syzbot] syzbot
2025-02-15 18:42 ` [syzbot] syzbot
2025-02-15 19:35 ` [syzbot] syzbot
2025-04-07 14:06 ` [syzbot] Arnaud Lecomte
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
2025-04-07 14:17   ` [syzbot] syzbot
2025-04-07 14:17 ` [syzbot] Arnaud Lecomte
2025-02-12 13:41 [syzbot] [modules?] KMSAN: uninit-value in __request_module (6) syzbot
2025-02-13 14:21 ` [syzbot] syzbot
2025-02-13 18:22 ` [syzbot] syzbot
2025-02-12 10:57 [syzbot] [jfs?] KASAN: slab-out-of-bounds Read in ea_get (4) syzbot
2025-02-12 22:56 ` [syzbot] syzbot
2025-02-09  5:48 [syzbot] [isofs?] KMSAN: uninit-value in isofs_readdir syzbot
2025-02-09 23:50 ` [syzbot] syzbot
2025-02-11  1:00 ` [syzbot] syzbot
2025-02-04 15:33 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_ptr_v2_validate syzbot
2025-04-01  3:56 ` [syzbot] syzbot
2025-01-29  9:17 [syzbot] [bcachefs?] KMSAN: uninit-value in btree_interior_update_work syzbot
2025-04-01  3:57 ` [syzbot] syzbot
2025-01-17  6:14 [syzbot] [usb?] general protection fault in status_show syzbot
2025-01-17 15:41 ` [syzbot] syzbot
2025-01-12  6:45 [syzbot] [iommu?] UBSAN: shift-out-of-bounds in iova_bitmap_alloc syzbot
2025-01-12 11:58 ` [syzbot] syzbot
2025-01-11 13:37 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_readdir (2) syzbot
2025-04-01  3:59 ` [syzbot] syzbot
2025-01-11  0:40 [syzbot] [usb?] general protection fault in qt2_read_bulk_callback syzbot
2025-01-11 17:19 ` [syzbot] syzbot
2025-01-03  1:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_trans_start_alloc_update_noupdate syzbot
2025-04-01  3:58 ` [syzbot] syzbot
2025-01-02 14:45 [syzbot] [f2fs?] KASAN: slab-out-of-bounds Read in f2fs_getxattr syzbot
2025-01-07 22:19 ` [syzbot] syzbot
2025-01-08 14:13 ` [syzbot] syzbot
2025-01-01 20:55 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_inode_unpack (2) syzbot
2025-04-01  3:58 ` [syzbot] syzbot
2024-12-25  2:26 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in force_devcd_write syzbot
2024-12-26  3:43 ` [syzbot] syzbot
2024-12-24 14:42 [syzbot] [bcachefs?] KMSAN: uninit-value in __bch2_bkey_cmp_left_packed syzbot
2025-04-01  4:02 ` [syzbot] syzbot
2024-12-24  6:38 [syzbot] [input?] KASAN: null-ptr-deref Write in input_ff_create syzbot
2024-12-25 16:44 ` [syzbot] syzbot
2024-12-19 10:14 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dirent_rename (2) syzbot
2025-04-01  4:04 ` [syzbot] syzbot
2024-12-15  8:10 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_checksum_update (2) syzbot
2025-04-01  4:06 ` [syzbot] syzbot
2024-12-13 19:13 [syzbot] [bcachefs?] KMSAN: uninit-value in __build_ro_aux_tree syzbot
2025-04-01  4:03 ` [syzbot] syzbot
2024-12-13  7:56 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_xattr_validate syzbot
2025-04-01  4:06 ` [syzbot] syzbot
2025-04-01  4:07 ` [syzbot] syzbot
2024-12-04 17:36 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dev_freespace_init syzbot
2025-04-01  4:03 ` [syzbot] syzbot
2024-12-01  9:40 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_get syzbot
2025-04-01  3:59 ` [syzbot] syzbot
2024-12-01  8:34 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_ptrs_validate syzbot
2025-04-01  4:02 ` [syzbot] syzbot
2024-11-30 19:55 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_dirent_validate syzbot
2025-04-01  4:04 ` [syzbot] syzbot
2024-11-29 16:59 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_val_validate syzbot
2025-04-01  4:02 ` [syzbot] syzbot
2024-11-28  9:49 [syzbot] [bcachefs?] kernel BUG in bch2_get_scanned_nodes syzbot
2024-11-28 20:31 ` [syzbot] syzbot
2024-11-27 18:59 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bkey_cmp_packed_inlined (2) syzbot
2025-04-01  4:01 ` [syzbot] syzbot
2024-11-27  0:00 [syzbot] upstream build error (22) syzbot
2025-02-03 12:55 ` [syzbot] syzbot
2024-11-26  0:00 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_trans_start_alloc_update syzbot
2025-04-01  4:08 ` [syzbot] syzbot
2024-11-25 13:28 [syzbot] [bcachefs?] BUG: corrupted list in bch2_btree_and_journal_iter_exit syzbot
2024-11-28 20:12 ` [syzbot] syzbot
2024-11-25 13:28 [syzbot] [bcachefs?] kernel BUG in bch2_journal_pin_set syzbot
2024-11-28  3:23 ` [syzbot] syzbot
2024-11-25 13:05 [syzbot] [bcachefs?] kernel BUG in bch2_evacuate_bucket syzbot
2024-11-29  0:39 ` [syzbot] syzbot
2024-11-25  3:10 [syzbot] [bcachefs?] kernel BUG in __bch2_journal_pin_put syzbot
2024-11-28  3:00 ` [syzbot] syzbot
2024-11-22 18:44 [syzbot] [bcachefs?] kernel BUG in bch2_btree_pos_to_text (2) syzbot
2024-11-25  3:59 ` [syzbot] syzbot
2024-11-22 18:44 [syzbot] [bcachefs?] KMSAN: uninit-value in rw_aux_tree_set (2) syzbot
2025-04-01  4:09 ` [syzbot] syzbot
2024-11-22 15:15 [syzbot] [bcachefs?] kernel BUG in bch2_btree_root_read syzbot
2024-11-25  6:53 ` [syzbot] syzbot
2024-11-22 14:42 [syzbot] [netfilter?] KMSAN: uninit-value in ip6table_mangle_hook (3) syzbot
2024-12-14 22:16 ` [syzbot] syzbot
2024-12-14 22:21 ` [syzbot] syzbot
2024-12-15  2:34 ` [syzbot] syzbot
2024-11-21 12:40 [syzbot] [bcachefs?] kernel BUG in bch2_btree_node_lock_write syzbot
2024-11-28  3:12 ` [syzbot] syzbot
2024-11-19  7:33 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_inode_v3_validate syzbot
2025-04-01  4:08 ` [syzbot] syzbot
2024-11-18 21:41 [syzbot] [bcachefs?] kernel BUG in bch2_bucket_alloc_trans (3) syzbot
2024-11-25  6:54 ` [syzbot] syzbot
2024-11-17  8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_alloc_v4_validate (2) syzbot
2025-04-01  4:00 ` [syzbot] syzbot
2024-11-17  8:54 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_iter_init (2) syzbot
2025-04-01  4:07 ` [syzbot] syzbot
2024-11-12  3:25 [syzbot] [bcachefs?] possible deadlock in bch2_alloc_sectors_start_trans syzbot
2024-11-29  0:34 ` [syzbot] syzbot
2024-11-11  0:28 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_btree_node_check_topology syzbot
2025-04-01  4:10 ` [syzbot] syzbot
2024-11-09 15:43 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_hash_insert syzbot
2024-11-11  3:13 ` [syzbot] syzbot
2024-11-08 15:57 [syzbot] [bcachefs?] kernel BUG in bch2_rechecksum_bio syzbot
2024-11-29  0:32 ` [syzbot] syzbot
2024-11-06 13:58 [syzbot] [bcachefs?] KMSAN: uninit-value in bch2_bucket_alloc_early syzbot
2025-04-01  4:05 ` [syzbot] syzbot
2024-11-06 13:24 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_traverse_one syzbot
2024-11-28  3:27 ` [syzbot] syzbot
2024-10-30 16:39 [syzbot] [bcachefs?] kernel BUG in __bkey_unpack_pos syzbot
2024-11-08  5:02 ` [syzbot] syzbot
2024-10-28 15:49 [syzbot] [bcachefs?] kernel BUG in bch2_btree_write_buffer_flush_locked syzbot
2024-11-28  3:21 ` [syzbot] syzbot
2024-10-27  3:54 [syzbot] [bcachefs?] kernel BUG in bch2_inconsistent_error syzbot
2024-11-08  0:48 ` [syzbot] syzbot
2024-10-27  1:10 [syzbot] [bcachefs?] kernel BUG in bch2_bkey_pack_pos_lossy syzbot
2024-11-08  5:11 ` [syzbot] syzbot
2024-10-25  6:49 [syzbot] [bcachefs?] kernel BUG in __bch2_bkey_cmp_packed_format_checked syzbot
2024-11-08  0:34 ` [syzbot] syzbot
2024-10-25  6:49 [syzbot] [bcachefs?] kernel BUG in bch2_trans_node_iter_init syzbot
2024-11-08  3:21 ` [syzbot] syzbot
2024-10-25  6:48 [syzbot] [bcachefs?] general protection fault in bch2_btree_path_traverse_one syzbot
2024-11-27  8:09 ` [syzbot] syzbot
2024-10-25  6:48 [syzbot] [bcachefs?] kernel BUG in bch2_journal_res_get (2) syzbot
2024-11-08  3:28 ` [syzbot] syzbot
2024-10-24 17:47 [syzbot] [bcachefs?] kernel BUG in bch2_run_recovery_pass syzbot
2024-11-11  4:31 ` [syzbot] syzbot
2024-10-23 18:30 [syzbot] [bcachefs?] possible deadlock in __bch2_trans_relock syzbot
2024-11-28 23:06 ` [syzbot] syzbot
2024-10-23 14:27 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in validate_sb_layout syzbot
2024-10-26  0:49 ` [syzbot] syzbot
2024-10-23 11:21 [syzbot] [bcachefs?] kernel BUG in bch2_btree_path_level_init (2) syzbot
2024-11-11  3:14 ` [syzbot] syzbot
2024-10-23  4:12 [syzbot] [bcachefs?] kernel BUG in bch2_ptr_swab syzbot
2024-11-11 21:16 ` [syzbot] syzbot
2024-10-21 13:07 [syzbot] [bcachefs?] kernel BUG in bch2_dev_btree_bitmap_mark syzbot
2024-11-08  4:25 ` [syzbot] syzbot
2024-10-21  6:44 [syzbot] [bcachefs?] UBSAN: shift-out-of-bounds in bch2_alloc_to_text syzbot
2024-10-26  0:47 ` [syzbot] syzbot
2024-10-21  4:31 [syzbot] [bcachefs?] kernel BUG in __bch2_trans_commit syzbot
2024-11-08  0:18 ` [syzbot] syzbot
2024-10-18  7:37 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_cache_exit syzbot
2024-11-11  4:46 ` [syzbot] syzbot
2024-10-03 17:42 [syzbot] [bcachefs?] possible deadlock in bch2_replicas_entry_validate syzbot
2024-10-16  6:42 ` [syzbot] syzbot
2024-10-03  8:10 [syzbot] [bcachefs?] kernel BUG in __bch2_btree_node_write syzbot
2024-11-25  6:52 ` [syzbot] syzbot
2024-09-28  2:13 [syzbot] [bcachefs?] kernel BUG in bch2_fs_btree_write_buffer_exit syzbot
2024-11-08  3:04 ` [syzbot] syzbot
2024-09-18  7:28 [syzbot] [bcachefs?] WARNING in bch2_journal_flush_seq_async syzbot
2024-11-28 22:50 ` [syzbot] syzbot
2024-08-27  2:12 [syzbot] [sound?] WARNING in snd_pcm_open syzbot
2024-09-06 10:33 ` [syzbot] syzbot
2024-07-30  1:14 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in journal_entry_dev_usage_to_text syzbot
2024-11-11 21:03 ` [syzbot] syzbot
2024-07-24  8:59 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_remove_adv_monitor_sync syzbot
2024-12-05  1:58 ` [syzbot] syzbot
2024-12-23 22:19 ` [syzbot] syzbot
2024-07-17 13:39 [syzbot] [bcachefs?] general protection fault in bch2_checksum syzbot
2024-11-28 22:59 ` [syzbot] syzbot
2024-07-13 22:54 [syzbot] [bpf?] [trace?] possible deadlock in console_flush_all (3) syzbot
2025-06-19 20:48 ` [syzbot] syzbot
2024-07-10 20:55 [syzbot] [bcachefs?] kernel BUG in bch2_journal_noflush_seq syzbot
2024-11-28 22:12 ` [syzbot] syzbot
2024-06-14 12:16 [syzbot] [crypto?] [bcachefs?] BUG: unable to handle kernel paging request in crypto_skcipher_encrypt syzbot
2024-11-25  7:19 ` [syzbot] syzbot
     [not found] <mailman.217.1706634262.2961.pvrusb2@isely.net>
2024-02-15 16:26 ` [syzbot] syzbot
2024-01-12 20:14 [syzbot] upstream build error (21) syzbot
2024-06-20  8:00 ` [syzbot] syzbot
2024-01-05 17:32 [syzbot] [net?] memory leak in ___neigh_create (2) syzbot
2024-09-05 11:54 ` [syzbot] syzbot
2023-11-16 11:09 [syzbot] [kernel?] inconsistent lock state in __lock_task_sighand syzbot
2024-09-06 10:37 ` [syzbot] syzbot
2023-10-16  7:38 [syzbot] [kernel?] KASAN: slab-use-after-free Read in reweight_entity syzbot
2024-09-06 10:38 ` [syzbot] syzbot
2023-06-05  3:53 [syzbot] [ext4?] WARNING: locking bug in ext4_move_extents syzbot
2024-07-03  7:48 ` [syzbot] syzbot
2022-12-21  8:15 [syzbot] possible deadlock in page_cache_ra_unbounded syzbot
2025-01-08 16:11 ` [syzbot] syzbot
2022-10-17  7:43 [syzbot] possible deadlock in attr_data_get_block syzbot
2024-07-17  8:19 ` [syzbot] syzbot
2022-09-25 11:18 [syzbot] WARNING in __change_page_attr_set_clr syzbot
2024-09-06 10:39 ` [syzbot] syzbot
2022-07-12 12:03 [syzbot] inconsistent lock state in find_vmap_area syzbot
2024-09-06 10:36 ` [syzbot] syzbot
2022-02-10 19:17 [syzbot] general protection fault in blk_mq_free_rqs syzbot
2023-11-10 18:56 ` [syzbot] syzbot
2021-02-26 14:48 general protection fault in try_to_wake_up (2) syzbot
2024-07-25 16:29 ` [syzbot] syzbot
2021-02-01 10:07 BUG: Bad page state (8) syzbot
2024-10-28 14:11 ` [syzbot] syzbot
2020-11-21  1:55 INFO: task can't die in shrink_inactive_list (2) syzbot
2024-09-06 10:39 ` [syzbot] syzbot
2020-10-13 17:02 WARNING in drop_nlink (2) syzbot
2024-11-20 15:35 ` [syzbot] syzbot
2020-08-08 21:27 KASAN: use-after-free Read in __queue_work (3) syzbot
2024-09-06 10:40 ` [syzbot] syzbot
2020-08-04 15:46 KASAN: use-after-free Read in __sco_sock_close syzbot
2024-09-06 10:35 ` [syzbot] syzbot
2018-11-24 19:40 WARNING in csum_and_copy_to_iter syzbot
2023-11-24 10:30 ` [syzbot] syzbot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).