From: sashiko-bot@kernel.org
To: "Haoli Zhang" <26031212468@stu.xidian.edu.cn>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v4] tracing: ring-buffer: fix stale reader-page link
Date: Fri, 13 Nov 2026 03:51:16 +0000 [thread overview]
Message-ID: <sashiko-outbox-212140@kernel.org> (raw)
In-Reply-To: <20261113033612.1349-1-26031212468@stu.xidian.edu.cn>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] tracing: ring-buffer: reply text in changelog and missing Fixes
trailer
--
commit c4296f8629e0420816a4b5f1c95a30a1141d5523
Author: Haoli Zhang <26031212468@stu.xidian.edu.cn>
> tracing: ring-buffer: fix stale reader-page link
>
> Hi Steve,
>
> Thanks for reviewing v3. I apologize for adding unnecessary NMI reader
> coordination and skip handling. You noted the report is unrelated to NMI
> reads. The lockless NMI path is only a best-effort crash-dump path.
> I have removed that complexity and dropped the Fixes tag.
>
> The report shows rb_is_reader_page() dereferencing a freed page through
> page->list.prev->next. During shrink, reader_page is detached from the
> ring list and can retain a previous link to a page being removed. Redirect
> that link to the surviving tail page while identifying pages to remove,
> before any removed page is freed.
>
> This change does not add work to the normal writer fast path or alter NMI
> reader behavior.
>
> Reported-by: syzbot+37e1793bdb0061ea3a47@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=37e1793bdb0061ea3a47
> Co-developed-by: Jinning Zhang <25031212117@stu.xidian.edu.cn>
> Signed-off-by: Jinning Zhang <25031212117@stu.xidian.edu.cn>
> Co-developed-by: Bin Yu <byu@xidian.edu.cn>
> Signed-off-by: Bin Yu <byu@xidian.edu.cn>
> Signed-off-by: Haoli Zhang <26031212468@stu.xidian.edu.cn>
[Severity: Low]
The opening paragraph ("Hi Steve, ...") is a personal reply to a reviewer
and should go below the "---" separator line so it is not recorded in git
history.
Also, since commit 83f40318dab0 ("ring-buffer: Make removal of ring buffer
pages atomic") rewrote rb_remove_pages() to unlink pages in place without
calling rb_reset_cpu() to reinitialize cpu_buffer->reader_page->list,
should this include:
Fixes: 83f40318dab0 ("ring-buffer: Make removal of ring buffer pages atomic")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113033612.1349-1-26031212468@stu.xidian.edu.cn?part=1
prev parent reply other threads:[~2026-11-13 3:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 3:36 [PATCH v4] tracing: ring-buffer: fix stale reader-page link Haoli Zhang
2026-11-13 3:51 ` sashiko-bot [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=sashiko-outbox-212140@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=26031212468@stu.xidian.edu.cn \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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