From: Hillf Danton <hdanton@sina.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Dmitry Vyukov <dvyukov@google.com>, Dan Carpenter <error27@gmail.com>
Subject: Re: some works in 2023
Date: Thu, 12 Oct 2023 05:18:46 +0800 [thread overview]
Message-ID: <20231011211846.1345-1-hdanton@sina.com> (raw)
In-Reply-To: <20230831115730.4806-1-hdanton@sina.com>
In 2023 alone (continued 2)
101 Subject: Re: [syzbot] [kernel?] general protection fault in netdev_register_kobject
https://yhbt.net/lore/lkml/000000000000bc839e060436421f@google.com/
102 Subject: Re: [syzbot] [kernel?] KASAN: slab-use-after-free Read in pwq_release_workfn
https://yhbt.net/lore/lkml/000000000000a178f50604369403@google.com/
103 Subject: Re: [syzbot] [net?] [wireless?] INFO: rcu detected stall in request_firmware_work_func
https://lore.kernel.org/lkml/0000000000001d0fac060436e0b4@google.com/
104 Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in __sco_sock_close
https://lore.kernel.org/lkml/0000000000002e6fcd0604566075@google.com/
105 Subject: Re: [syzbot] [kernel?] general protection fault in tty_register_device_attr
https://lore.kernel.org/lkml/000000000000a1ef37060459de79@google.com/
106 Subject: Re: [syzbot] [kernel?] KASAN: slab-use-after-free Read in dev_uevent
https://lore.kernel.org/lkml/000000000000be767106045cc22d@google.com/
107 Subject: Re: [syzbot] [afs?] KASAN: slab-use-after-free Read in afs_dynroot_test_super
https://lore.kernel.org/lkml/00000000000079a09a0604692e94@google.com/
108 Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in sco_conn_del
https://lore.kernel.org/lkml/0000000000000598e50604b668a1@google.com/
109 Subject: Re: [syzbot] [mm?] kernel BUG in vma_replace_policy
https://lore.kernel.org/lkml/0000000000004554cd0604e5bcc5@google.com/
110 Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Read in team_device_event
https://lore.kernel.org/lkml/0000000000000c7f5d0604f924b5@google.com/
111 Subject: Re: [syzbot] [bluetooth?] general protection fault in lock_sock_nested
https://lore.kernel.org/lkml/0000000000004af49b06051546ab@google.com/
112 Subject: Re: [syzbot] [reiserfs?] possible deadlock in super_lock
https://lore.kernel.org/lkml/000000000000e6665c0605ff20f6@google.com/
113 Subject: Re: [syzbot] [netfilter?] INFO: rcu detected stall in gc_worker (3)
https://lore.kernel.org/lkml/00000000000076fc0706062e0619@google.com/
114 Subject: Re: [syzbot] [bluetooth?] possible deadlock in hci_dev_do_close
https://lore.kernel.org/lkml/000000000000a559aa06062dc990@google.com/
115 Subject: Re: [syzbot] [serial?] KASAN: use-after-free Read in gsm_cleanup_mux
https://lore.kernel.org/lkml/0000000000005c26700606418357@google.com/
116 Subject: Re: [syzbot] [pvrusb2?] KASAN: slab-use-after-free Read in pvr2_context_set_notify
https://lore.kernel.org/lkml/0000000000001bacdb060669b7d8@google.com/
117 Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Read in tls_encrypt_done
https://lore.kernel.org/lkml/00000000000015a94a06068f132c@google.com/
118 Subject: Re: [syzbot] [mm?] WARNING in copy_hugetlb_page_range
https://lore.kernel.org/lkml/0000000000003ee4a70606d9d0c1@google.com/
119 Subject: Re: [syzbot] [net?] [usb?] INFO: rcu detected stall in worker_thread (9)
https://lore.kernel.org/lkml/0000000000006cdc4c060732e606@google.com/
120 Subject: Re: [syzbot] [kernel?] INFO: rcu detected stall in clock_adjtime (2)
https://lore.kernel.org/lkml/000000000000a8ec770607334a74@google.com/
121 Subject: Re: [syzbot] [reiserfs?] possible deadlock in super_lock
https://lore.kernel.org/lkml/000000000000e45bec06075b4cc8@google.com/
122 Subject: Re: [syzbot] [reiserfs?] possible deadlock in filename_create
https://lore.kernel.org/lkml/00000000000090cd01060770a5e2@google.com/
next prev parent reply other threads:[~2023-10-11 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 11:14 Hillf Danton
2023-08-31 11:57 ` Hillf Danton
2023-10-11 21:18 ` Hillf Danton [this message]
2023-10-12 7:26 ` Dmitry Vyukov
2023-12-30 5:09 ` Hillf Danton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231011211846.1345-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=dvyukov@google.com \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox