From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/lease: cap object_count to avoid order > MAX_PAGE_ORDER warning
Date: Wed, 27 May 2026 15:13:21 +1000 [thread overview]
Message-ID: <review-overall-20260526055359.17392-1-devnexen@gmail.com> (raw)
In-Reply-To: <20260526055359.17392-1-devnexen@gmail.com>
Overall Series Review
Subject: drm/lease: cap object_count to avoid order > MAX_PAGE_ORDER warning
Author: David Carlier <devnexen@gmail.com>
Patches: 1
Reviewed: 2026-05-27T15:13:21.349922
---
This is a single patch fixing a syzbot-reported bug where an unbounded `object_count` from userspace causes `kzalloc_objs()` to request an allocation large enough to trigger a `WARN_ON_ONCE_GFP` in the page allocator. The fix is straightforward and correct in principle: cap the count at the ioctl entry point before the allocation happens. The approach is reasonable and the placement is right. There are a couple of minor issues worth discussing.
**Verdict: Acceptable with minor nits.**
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-27 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 5:53 [PATCH] drm/lease: cap object_count to avoid order > MAX_PAGE_ORDER warning David Carlier
2026-05-27 5:13 ` Claude Code Review Bot [this message]
2026-05-27 5:13 ` 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-overall-20260526055359.17392-1-devnexen@gmail.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