From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot ci <syzbot+ci9dceb132e443f5a7@syzkaller.appspotmail.com>
Cc: linux-mm@kvack.org, ljykernel@163.com, syzbot@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot ci] Re: mm/page_owner: warn when stack trace depth hits PAGE_OWNER_STACK_DEPTH limit
Date: Sat, 28 Mar 2026 10:39:59 -0700 [thread overview]
Message-ID: <20260328103959.a4739ffff3c8d7a6f4d60732@linux-foundation.org> (raw)
In-Reply-To: <69c80fa8.a70a0220.97f31.0002.GAE@google.com>
On Sat, 28 Mar 2026 10:28:08 -0700 syzbot ci <syzbot+ci9dceb132e443f5a7@syzkaller.appspotmail.com> wrote:
> syzbot ci has tested the following series
>
> [v2] mm/page_owner: warn when stack trace depth hits PAGE_OWNER_STACK_DEPTH limit
> https://lore.kernel.org/all/20260328214408.2990597-1-ljykernel@163.com
> * [PATCH v2] mm/page_owner: warn when stack trace depth hits PAGE_OWNER_STACK_DEPTH limit
>
> and found the following issue:
> possible deadlock in hrtimer_start_range_ns
>
> Full report is available here:
> https://ci.syzbot.org/series/aa38ba8f-44db-4d01-8965-ed5a27174f71
>
> ***
>
> possible deadlock in hrtimer_start_range_ns
Thanks. Sashiko reported a couple of things, one of which is a deadlock,
probably the same one:
https://sashiko.dev/#/patchset/20260328214408.2990597-1-ljykernel@163.com
next prev parent reply other threads:[~2026-03-28 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <JR421L42D7V@zendesk.com>
2026-03-28 21:44 ` [PATCH v2] " Jiayuan Liang
2026-03-28 17:28 ` [syzbot ci] " syzbot ci
2026-03-28 17:28 ` Request received Yail
2026-03-28 17:39 ` Andrew Morton [this message]
2026-03-30 20:48 ` [PATCH v2] mm/page_owner: warn when stack trace depth hits PAGE_OWNER_STACK_DEPTH limit Andrew Morton
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=20260328103959.a4739ffff3c8d7a6f4d60732@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=ljykernel@163.com \
--cc=syzbot+ci9dceb132e443f5a7@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
/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