mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+1827030ed7bc886dd0a5@syzkaller.appspotmail.com>
To: emmaonana18@gmail.com
Cc: emmaonana18@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in stack_depot_save_flags (2)
Date: Wed, 11 Nov 2026 13:00:47 -0800	[thread overview]
Message-ID: <6af4d77f.b1d299f9.122b8e.0001.GAE@google.com> (raw)
In-Reply-To: <20261111210000.302485-1-emmaonana18@gmail.com>

> #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

Patch testing via #syz test is temporarily disabled.
See https://github.com/google/syzkaller/issues/8122 for details.

>
> diff --git a/lib/stackdepot.c b/lib/stackdepot.c
> index 90c52f2e0d3f4..da4dba8b40bd3 100644
> --- a/lib/stackdepot.c
> +++ b/lib/stackdepot.c
> @@ -299,7 +299,13 @@ static bool depot_init_pool(void **prealloc)
>  		/* Bail out if we reached the pool limit. */
>  		WARN_ON_ONCE(pools_num > stack_max_pools); /* should never happen */
>  		WARN_ON_ONCE(!new_pool); /* to avoid unnecessary pre-allocation */
> -		WARN_ONCE(1, "Stack depot reached limit capacity");
> +		/*
> +		 * Exhaustion is a handled resource limit, not a bug:
> +		 * all users cope with a failed save, and privileged workloads
> +		 * (e.g. BPF JIT churning unique stacks under KASAN) can reach
> +		 * it legitimately. Keep a one-time notice, not a WARN() splat.
> +		 */
> +		pr_warn_once("Stack depot reached limit capacity");
>  		return false;
>  	}
>  

       reply	other threads:[~2026-11-11 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261111210000.302485-1-emmaonana18@gmail.com>
2026-11-11 21:00 ` syzbot [this message]
2026-05-19 17:48 syzbot
2026-08-15 12:36 ` syzbot

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=6af4d77f.b1d299f9.122b8e.0001.GAE@google.com \
    --to=syzbot+1827030ed7bc886dd0a5@syzkaller.appspotmail.com \
    --cc=emmaonana18@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.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

all inboxes | Powered by JetHome®