From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: relay: zero page->private when freeing pages
Date: Tue, 24 Feb 2026 10:52:52 +1000 [thread overview]
Message-ID: <review-patch1-20260223032641.1859381-2-ziy@nvidia.com> (raw)
In-Reply-To: <20260223032641.1859381-2-ziy@nvidia.com>
Patch Review
There is a bug in the depopulate error path. The patch uses `i` when it should use `j`:
> depopulate:
> - for (j = 0; j < i; j++)
> + for (j = 0; j < i; j++) {
> + set_page_private(buf->page_array[i], 0);
> __free_page(buf->page_array[j]);
> + }
The `set_page_private` call uses `buf->page_array[i]`, but at the `depopulate` label, `i` is the index where `alloc_page()` failed. That means `buf->page_array[i]` is NULL (the allocation returned NULL). This will cause a NULL pointer dereference in `set_page_private`. The correct index is `j`, matching the `__free_page` call on the next line.
The second hunk in `relay_destroy_buf` correctly uses `i` for both calls since the same loop variable is used throughout:
> - for (i = 0; i < buf->page_count; i++)
> + for (i = 0; i < buf->page_count; i++) {
> + set_page_private(buf->page_array[i], 0);
> __free_page(buf->page_array[i]);
> + }
This part is correct.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-24 0:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 3:26 [PATCH v1 00/11] Zero page->private when freeing pages Zi Yan
2026-02-23 3:26 ` [PATCH v1 01/11] relay: zero " Zi Yan
2026-02-23 14:45 ` Usama Arif
2026-02-24 0:52 ` Claude Code Review Bot [this message]
2026-02-23 3:26 ` [PATCH v1 02/11] mm/slub: " Zi Yan
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 3:26 ` [PATCH v1 03/11] drm/ttm: " Zi Yan
2026-02-23 10:43 ` Christian König
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 3:26 ` [PATCH v1 04/11] blk-mq: " Zi Yan
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 3:26 ` [PATCH v1 05/11] watch_queue: " Zi Yan
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 3:26 ` [PATCH v1 06/11] binder: " Zi Yan
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 3:26 ` [PATCH v1 07/11] null_blk: " Zi Yan
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 3:26 ` [PATCH v1 08/11] percpu: " Zi Yan
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 3:26 ` [PATCH v1 09/11] erofs: " Zi Yan
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 3:26 ` [PATCH v1 10/11] mm/huge_memory: add page->private check back in __split_folio_to_order() Zi Yan
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 3:26 ` [PATCH v1 11/11] mm/page_alloc: check page->private upon page free Zi Yan
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
2026-02-23 4:28 ` [PATCH v1 00/11] Zero page->private when freeing pages Matthew Wilcox
2026-02-23 9:36 ` David Hildenbrand (Arm)
2026-02-23 8:40 ` [syzbot ci] " syzbot ci
[not found] ` <aZxaIEFZr2NvO2eQ@infradead.org>
2026-02-23 14:00 ` [PATCH v1 00/11] " Zi Yan
[not found] ` <aZxeLmNyKKTrkSzn@infradead.org>
2026-02-23 14:11 ` Zi Yan
2026-02-23 14:06 ` Christian König
2026-02-23 14:14 ` David Hildenbrand (Arm)
2026-02-23 15:22 ` Christian König
2026-02-23 15:27 ` David Hildenbrand (Arm)
2026-02-24 0:52 ` Claude review: " Claude Code Review Bot
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=review-patch1-20260223032641.1859381-2-ziy@nvidia.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.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