Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.org>
To: Erhard Furtner <erhard_f@mailbox.org>, linux-kernel@vger.kernel.org
Cc: linux-cifs@vger.kernel.org, David Howells <dhowells@redhat.com>,
	netfs@lists.linux.dev
Subject: Re: client side "current->alloc_tag not set WARNING: ./include/linux/alloc_tag.h:161" at accessing CIFS share
Date: Tue, 01 Sep 2026 20:19:27 -0300	[thread overview]
Message-ID: <0e8961201179ba88038de511c587ddc7@manguebit.org> (raw)
In-Reply-To: <0b004319-9ef7-437c-a4dd-174d6a9a83db@mailbox.org>

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.

      reply	other threads:[~2026-09-01 23:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 14:54 client side "current->alloc_tag not set WARNING: ./include/linux/alloc_tag.h:161" at accessing CIFS share Erhard Furtner
2026-09-01 23:19 ` Paulo Alcantara [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=0e8961201179ba88038de511c587ddc7@manguebit.org \
    --to=pc@manguebit.org \
    --cc=dhowells@redhat.com \
    --cc=erhard_f@mailbox.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfs@lists.linux.dev \
    /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