From: Greg KH <greg@kroah.com>
To: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
Cc: stable@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 5.15,5.10,5.4,4.19 0/2] Fix warning when tracing with large filenames
Date: Mon, 29 Apr 2024 13:06:29 +0200 [thread overview]
Message-ID: <2024042923-attribute-brunt-15b5@gregkh> (raw)
In-Reply-To: <20240424222010.2547286-1-cascardo@igalia.com>
On Wed, Apr 24, 2024 at 07:20:07PM -0300, Thadeu Lima de Souza Cascardo wrote:
> The warning described on patch "tracing: Increase PERF_MAX_TRACE_SIZE to
> handle Sentinel1 and docker together" can be triggered with a perf probe on
> do_execve with a large path. As PATH_MAX is larger than PERF_MAX_TRACE_SIZE
> (2048 before the patch), the warning will trigger.
>
> The fix was included in 5.16, so backporting to 5.15 and earlier LTS
> kernels. Also included is a patch that better describes the attempted
> allocation size.
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-04-29 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 22:20 [PATCH 5.15,5.10,5.4,4.19 0/2] Fix warning when tracing with large filenames Thadeu Lima de Souza Cascardo
2024-04-24 22:20 ` [PATCH 5.15,5.10,5.4,4.19 1/2] tracing: Show size of requested perf buffer Thadeu Lima de Souza Cascardo
2024-04-24 22:20 ` [PATCH 5.15,5.10 2/2] tracing: Increase PERF_MAX_TRACE_SIZE to handle Sentinel1 and docker together Thadeu Lima de Souza Cascardo
2024-04-24 22:20 ` [PATCH 5.4,4.19 " Thadeu Lima de Souza Cascardo
2024-04-29 11:06 ` Greg KH [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=2024042923-attribute-brunt-15b5@gregkh \
--to=greg@kroah.com \
--cc=cascardo@igalia.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.