mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
	audit@vger.kernel.org, "open list" <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	"Linux Regressions" <regressions@lists.linux.dev>
Cc: "Eric Paris" <eparis@redhat.com>,
	"Paul Moore" <paul@paul-moore.com>,
	"Dan Carpenter" <dan.carpenter@linaro.org>,
	"Anders Roxell" <anders.roxell@linaro.org>,
	"Yafang Shao" <laoar.shao@gmail.com>
Subject: Re: include/linux/fortify-string.h:293:17: error: call to '__write_overflow' declared with attribute error: detected write beyond size of object (1st parameter)
Date: Tue, 26 Nov 2024 16:12:45 +0100	[thread overview]
Message-ID: <29ab783d-86e2-4528-a6ad-083f8baf56d1@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYvWkS-8f9kOBTzixjGSNN8262StoVv2ERk7mRKcU+p+BA@mail.gmail.com>

On Tue, Nov 26, 2024, at 15:58, Naresh Kamboju wrote:
> Build error:
> ---------
> In function 'sized_strscpy',
>     inlined from '__audit_ptrace' at kernel/auditsc.c:2732:2:
> include/linux/fortify-string.h:293:17: error: call to
> '__write_overflow' declared with attribute error: detected write
> beyond size of object (1st parameter)
>   293 |                 __write_overflow();
>       |                 ^~~~~~~~~~~~~~~~~~
> In function 'sized_strscpy',
>     inlined from 'audit_signal_info_syscall' at kernel/auditsc.c:2759:3:
> include/linux/fortify-string.h:293:17: error: call to
> '__write_overflow' declared with attribute error: detected write
> beyond size of object (1st parameter)
>   293 |                 __write_overflow();
>       |                 ^~~~~~~~~~~~~~~~~~
> make[4]: *** [scripts/Makefile.build:229: kernel/auditsc.o] Error 1

I have run into this specific one before but failed to
come up with a working fix.

I think the specific warning started with

https://lore.kernel.org/all/20240828030321.20688-3-laoar.shao@gmail.com/

but reverting that just replaces it with a slightly different
warning. In my randconfig tree I have a patch that comments out
the two security_task_getlsmprop_obj(), and I don't think I get
warnings at the moment, but I no longer see why I would have done
that.

      Arnd

  reply	other threads:[~2024-11-26 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 14:58 Naresh Kamboju
2024-11-26 15:12 ` Arnd Bergmann [this message]
2024-11-26 16:26   ` Arnd Bergmann

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=29ab783d-86e2-4528-a6ad-083f8baf56d1@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=anders.roxell@linaro.org \
    --cc=audit@vger.kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=eparis@redhat.com \
    --cc=laoar.shao@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=paul@paul-moore.com \
    --cc=regressions@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

all inboxes | Powered by JetHome®