From: Hillf Danton <hdanton@sina.com>
To: Hillf Danton <hdanton@sina.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: some debugging works
Date: Sat, 20 Aug 2022 06:08:27 +0800 [thread overview]
Message-ID: <20220819220827.1639-1-hdanton@sina.com> (raw)
In-Reply-To: <20220806130928.2034-1-hdanton@sina.com>
On Sat, 6 Aug 2022 21:09:28 +0800 Hillf Danton <hdanton@sina.com> wrote:
>
> In 2022 alone
...
> 7.85 trying to register non-static key in rxe_cleanup_task
> https://lore.kernel.org/lkml/000000000000280dfd05e5686579@google.com/
>
7.86 possible deadlock in ext4_xattr_get
https://lore.kernel.org/lkml/00000000000017bd2d05e5c47f10@google.com/
7.87 WARNING in blk_mq_release
https://lore.kernel.org/lkml/000000000000cc7ce805e5d4e158@google.com/
7.88 WARNING in hrtimer_init
https://lore.kernel.org/lkml/000000000000d12aa605e5d4a1e1@google.com/
7.89 possible deadlock in ext4_bmap
https://lore.kernel.org/lkml/000000000000a7290705e5d46441@google.com/
7.90 possible deadlock in p9_req_put
https://lore.kernel.org/lkml/000000000000013bb605e5d40423@google.com/
7.91 trying to register non-static key in gsmld_write
https://lore.kernel.org/lkml/000000000000f44a2905e5e5a89e@google.com/
7.92 task hung in __generic_file_fsync
https://lore.kernel.org/lkml/000000000000a9029805e5f71478@google.com/
7.93 WARNING in tls_strp_done
https://lore.kernel.org/lkml/00000000000001dffa05e6348db4@google.com/
7.94 use-after-free Read in send_packet
https://lore.kernel.org/lkml/0000000000003809f605e65a4b5f@google.com/
7.95 WARNING: suspicious RCU usage in bpf_sk_reuseport_detach
https://lore.kernel.org/lkml/0000000000004f0e5705e65a96f2@google.com/
7.96 use-after-free Read in mgmt_pending_remove
https://lore.kernel.org/lkml/00000000000057a3a805e66ebf28@google.com/
7.97 general protection fault in hci_uart_tty_ioctl
https://lore.kernel.org/lkml/00000000000065234105e66e4531@google.com/
7.98 WARNING in __cancel_work
https://lore.kernel.org/lkml/000000000000dd3ef305e6889368@google.com/
7.99 INFO: rcu detected stall in watchdog
https://lore.kernel.org/lkml/000000000000eb202c05e6996c20@google.com/
7.100 possible deadlock in jbd2_journal_lock_updates
https://lore.kernel.org/lkml/000000000000761b3f05e69a3131@google.com/
prev parent reply other threads:[~2022-08-19 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 13:09 Hillf Danton
2022-08-19 22:08 ` Hillf Danton [this message]
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=20220819220827.1639-1-hdanton@sina.com \
--to=hdanton@sina.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