public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: "Li,Rongqing(ACG CCN)" <lirongqing@baidu.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Kees Cook <kees@kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: 答复: [PATCH] fs/coredump: reduce redundant log noise in validate_coredump_safety
Date: Wed, 22 Apr 2026 00:34:03 +0000	[thread overview]
Message-ID: <7cb39b3d208649fa984ce5c9b4f7f5b4@baidu.com> (raw)
In-Reply-To: <20260410080918.2319-1-lirongqing@baidu.com>


> From: Li RongQing <lirongqing@baidu.com>
> 
> Currently, writing to 'core_pattern' or 'suid_dumpable' sysctl nodes always
> triggers validate_coredump_safety(), even if the values have not changed. This
> results in redundant warning messages in dmesg:
> 
> "Unsafe core_pattern used with fs.suid_dumpable=2..."
> 
> This patch optimizes the procfs handlers to only invoke the safety validation
> when an actual change in the configuration is detected:
> 
> 1. In proc_dostring_coredump(), compare the new core_pattern string
>    with the existing one using strncmp().
> 2. In proc_dointvec_minmax_coredump(), check if the new suid_dumpable
>    value differs from the previous one.
> 
> This keeps the kernel log clean from repetitive warnings when re-applying the
> same sysctl settings.
> 
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> ---
>  fs/coredump.c | 3 ++-
>  fs/exec.c     | 6 ++++--
>  2 files changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/coredump.c b/fs/coredump.c index 29df8aa..9b357d2 100644
> --- a/fs/coredump.c
> +++ b/fs/coredump.c
> @@ -1483,7 +1483,8 @@ static int proc_dostring_coredump(const struct
> ctl_table *table, int write,
>  		return -EINVAL;
>  	}
> 
> -	validate_coredump_safety();
> +	if (strncmp(old_core_pattern, core_pattern, CORENAME_MAX_SIZE))
> +		validate_coredump_safety();
>  	return error;
>  }
> 
> diff --git a/fs/exec.c b/fs/exec.c
> index 9ea3a77..32b46e4 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -1975,9 +1975,11 @@ COMPAT_SYSCALL_DEFINE5(execveat, int, fd,
> static int proc_dointvec_minmax_coredump(const struct ctl_table *table, int
> write,
>  		void *buffer, size_t *lenp, loff_t *ppos)  {
> -	int error = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
> +	int error, old = READ_ONCE(suid_dumpable);
> 
> -	if (!error && write)
> +	error = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
> +
> +	if (!error && write && (old != READ_ONCE(suid_dumpable)))
>  		validate_coredump_safety();
>  	return error;
>  }
> --
> 2.9.4

Ping 
Thanks

[Li,Rongqing] 


  reply	other threads:[~2026-04-22  0:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  8:09 [PATCH] fs/coredump: reduce redundant log noise in validate_coredump_safety lirongqing
2026-04-22  0:34 ` Li,Rongqing(ACG CCN) [this message]
2026-04-22 12:44 ` Christian Brauner

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=7cb39b3d208649fa984ce5c9b4f7f5b4@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=kees@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=viro@zeniv.linux.org.uk \
    /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