* Re: client side "current->alloc_tag not set WARNING: ./include/linux/alloc_tag.h:161" at accessing CIFS share
[not found] <0b004319-9ef7-437c-a4dd-174d6a9a83db@mailbox.org>
@ 2026-09-01 23:19 ` Paulo Alcantara
0 siblings, 0 replies; only message in thread
From: Paulo Alcantara @ 2026-09-01 23:19 UTC (permalink / raw)
To: Erhard Furtner, linux-kernel; +Cc: linux-cifs, David Howells, netfs
Erhard Furtner <erhard_f@mailbox.org> writes:
> Getting this "current->alloc_tag not set WARNING:" every time on my
> client PC when I open files on the CIFS share (exported via KSMBD) from
> my host PC:
The warning is triggered by running the following in
netfs_alloc_request() with CONFIG_MEM_ALLOC_PROFILING_DEBUG=y kernels:
rreq = mempool->alloc(gfp, mempool->pool_data);
for the non-writeback path.
@mempool->alloc is set to mempool_alloc_slab(), which calls
kmem_cache_alloc_noprof() directly and expects the caller to have
already set current->alloc_tag.
It doesn't occur in the writeback path, however, because we call
mempool_alloc() macro that wraps to
alloc_hooks(mempool_alloc_noprof(...))
and it sets current->alloc_tag before the allocation.
I'll look for a possible solution and then let you know.
Thanks for the report.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-09-01 23:19 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <0b004319-9ef7-437c-a4dd-174d6a9a83db@mailbox.org>
2026-09-01 23:19 ` client side "current->alloc_tag not set WARNING: ./include/linux/alloc_tag.h:161" at accessing CIFS share Paulo Alcantara
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox