From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: William Theesfeld <william@theesfeld.net>,
Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: convert dquot iterator map allocation to kmalloc_array()
Date: Mon, 1 Jun 2026 22:56:47 -0700 [thread overview]
Message-ID: <ah5wn3fk1ijxEVNy@infradead.org> (raw)
In-Reply-To: <20260602051444.GU6078@frogsfrogsfrogs>
On Mon, Jun 01, 2026 at 10:14:44PM -0700, Darrick J. Wong wrote:
> Macros these days...
In in the new world order this should be kmalloc_objs anyway.
And when we touch this, we should probably drop the NOFAIL and add
allocation failure handling.
next prev parent reply other threads:[~2026-06-02 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 19:18 William Theesfeld
2026-06-02 5:14 ` Darrick J. Wong
2026-06-02 5:56 ` Christoph Hellwig [this message]
2026-06-02 11:25 ` [PATCH v2] xfs: convert dquot iterator map allocation to kmalloc_objs() William Theesfeld
2026-06-02 14:01 ` Carlos Maiolino
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=ah5wn3fk1ijxEVNy@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=william@theesfeld.net \
/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
all inboxes | Powered by JetHome®