From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Jan Kara <jack@suse.cz>, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 5.15] udf: Allocate name buffer in directory iterator on heap
Date: Fri, 15 Nov 2024 10:20:48 +0900 [thread overview]
Message-ID: <20241115012048.GK1458936@google.com> (raw)
In-Reply-To: <ZzZB9-DX7IWbfSXs@sashalap>
On (24/11/14 13:31), Sasha Levin wrote:
> On Wed, Nov 13, 2024 at 01:30:35PM +0900, Sergey Senozhatsky wrote:
> > From: Jan Kara <jack@suse.cz>
> >
> > [ Upstream commit 0aba4860b0d0216a1a300484ff536171894d49d8 ]
> >
> > Currently we allocate name buffer in directory iterators (struct
> > udf_fileident_iter) on stack. These structures are relatively large
> > (some 360 bytes on 64-bit architectures). For udf_rename() which needs
> > to keep three of these structures in parallel the stack usage becomes
> > rather heavy - 1536 bytes in total. Allocate the name buffer in the
> > iterator from heap to avoid excessive stack usage.
> >
> > Link: https://lore.kernel.org/all/202212200558.lK9x1KW0-lkp@intel.com
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Jan Kara <jack@suse.cz>
>
> Your S-O-B is missing, but also it doesn't build:
OK, didn't know that I need to add my SoB.
> fs/udf/directory.c: In function 'udf_fiiter_init':
> fs/udf/directory.c:251:25: error: implicit declaration of function 'kmalloc'; did you mean 'kvmalloc'? [-Werror=implicit-function-declaration]
> 251 | iter->namebuf = kmalloc(UDF_NAME_LEN_CS0, GFP_KERNEL);
> | ^~~~~~~
> | kvmalloc
> fs/udf/directory.c:251:23: warning: assignment to 'uint8_t *' {aka 'unsigned char *'} from 'int' makes pointer from integer without a cast [-Wint-conversion]
> 251 | iter->namebuf = kmalloc(UDF_NAME_LEN_CS0, GFP_KERNEL);
> | ^
> fs/udf/directory.c: In function 'udf_fiiter_release':
> fs/udf/directory.c:315:9: error: implicit declaration of function 'kfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
> 315 | kfree(iter->namebuf);
> | ^~~~~
> | kvfree
Hmm. Upstream fs/udf/directory.c doesn't include slab.h and 5.15
with this patch applied "builds on my computer". So I can amend
Jan's patch to include slab.h, I guess? Is that okay?
prev parent reply other threads:[~2024-11-15 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 4:30 [PATCH 5.15] udf: Allocate name buffer in directory iterator on heap Sergey Senozhatsky
2024-11-14 18:31 ` Sasha Levin
2024-11-15 1:20 ` Sergey Senozhatsky [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=20241115012048.GK1458936@google.com \
--to=senozhatsky@chromium.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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