From: James Morris <jmorris@namei.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: linux-kernel@vger.kernel.org, Martin Sebor <msebor@gcc.gnu.org>,
Serge Hallyn <serge@hallyn.com>, Arnd Bergmann <arnd@arndb.de>,
x86@kernel.org, Ning Sun <ning.sun@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Kalle Valo <kvalo@codeaurora.org>,
Simon Kelley <simon@thekelleys.org.uk>,
James Smart <james.smart@broadcom.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Anders Larsen <al@alarsen.net>, Tejun Heo <tj@kernel.org>,
Imre Deak <imre.deak@intel.com>,
linux-arm-kernel@lists.infradead.org,
tboot-devel@lists.sourceforge.net,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-scsi@vger.kernel.org,
cgroups@vger.kernel.org, linux-security-module@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Kees Cook <keescook@chromium.org>,
Miklos Szeredi <mszeredi@redhat.com>,
Tycho Andersen <tycho@tycho.pizza>
Subject: Re: [PATCH 03/11] security: commoncap: fix -Wstringop-overread warning
Date: Thu, 25 Mar 2021 07:50:33 +1100 (AEDT) [thread overview]
Message-ID: <b8ebab59-1cec-42d-6fb9-44aa1a464ae2@namei.org> (raw)
In-Reply-To: <20210322160253.4032422-4-arnd@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Mon, 22 Mar 2021, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> gcc-11 introdces a harmless warning for cap_inode_getsecurity:
>
> security/commoncap.c: In function ‘cap_inode_getsecurity’:
> security/commoncap.c:440:33: error: ‘memcpy’ reading 16 bytes from a region of size 0 [-Werror=stringop-overread]
> 440 | memcpy(&nscap->data, &cap->data, sizeof(__le32) * 2 * VFS_CAP_U32);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The problem here is that tmpbuf is initialized to NULL, so gcc assumes
> it is not accessible unless it gets set by vfs_getxattr_alloc(). This is
> a legitimate warning as far as I can tell, but the code is correct since
> it correctly handles the error when that function fails.
>
> Add a separate NULL check to tell gcc about it as well.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git fixes-v5.12
--
James Morris
<jmorris@namei.org>
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris@namei.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: linux-kernel@vger.kernel.org, Martin Sebor <msebor@gcc.gnu.org>,
Serge Hallyn <serge@hallyn.com>, Arnd Bergmann <arnd@arndb.de>,
x86@kernel.org, Ning Sun <ning.sun@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Kalle Valo <kvalo@codeaurora.org>,
Simon Kelley <simon@thekelleys.org.uk>,
James Smart <james.smart@broadcom.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Anders Larsen <al@alarsen.net>, Tejun Heo <tj@kernel.org>,
Imre Deak <imre.deak@intel.com>,
linux-arm-kernel@lists.infradead.org,
tboot-devel@lists.sourceforge.net,
intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, ath11k@lists.infradead.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-scsi@vger.kernel.org, cgroups@vger.kernel.org,
linux-security-module@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Kees Cook <keescook@chromium.org>,
Miklos Szeredi <mszeredi@redhat.com>,
Tycho Andersen <tycho@tycho.pizza>
Subject: Re: [PATCH 03/11] security: commoncap: fix -Wstringop-overread warning
Date: Thu, 25 Mar 2021 07:50:33 +1100 (AEDT) [thread overview]
Message-ID: <b8ebab59-1cec-42d-6fb9-44aa1a464ae2@namei.org> (raw)
In-Reply-To: <20210322160253.4032422-4-arnd@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Mon, 22 Mar 2021, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> gcc-11 introdces a harmless warning for cap_inode_getsecurity:
>
> security/commoncap.c: In function ‘cap_inode_getsecurity’:
> security/commoncap.c:440:33: error: ‘memcpy’ reading 16 bytes from a region of size 0 [-Werror=stringop-overread]
> 440 | memcpy(&nscap->data, &cap->data, sizeof(__le32) * 2 * VFS_CAP_U32);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The problem here is that tmpbuf is initialized to NULL, so gcc assumes
> it is not accessible unless it gets set by vfs_getxattr_alloc(). This is
> a legitimate warning as far as I can tell, but the code is correct since
> it correctly handles the error when that function fails.
>
> Add a separate NULL check to tell gcc about it as well.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git fixes-v5.12
--
James Morris
<jmorris@namei.org>
[-- Attachment #2: Type: text/plain, Size: 102 bytes --]
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris@namei.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: linux-kernel@vger.kernel.org, Martin Sebor <msebor@gcc.gnu.org>,
Serge Hallyn <serge@hallyn.com>, Arnd Bergmann <arnd@arndb.de>,
x86@kernel.org, Ning Sun <ning.sun@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Kalle Valo <kvalo@codeaurora.org>,
Simon Kelley <simon@thekelleys.org.uk>,
James Smart <james.smart@broadcom.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Anders Larsen <al@alarsen.net>, Tejun Heo <tj@kernel.org>,
Imre Deak <imre.deak@intel.com>,
linux-arm-kernel@lists.infradead.org,
tboot-devel@lists.sourceforge.net,
intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, ath11k@lists.infradead.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-scsi@vger.kernel.org, cgroups@vger.kernel.org,
linux-security-module@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Kees Cook <keescook@chromium.org>,
Miklos Szeredi <mszeredi@redhat.com>,
Tycho Andersen <tycho@tycho.pizza>
Subject: Re: [PATCH 03/11] security: commoncap: fix -Wstringop-overread warning
Date: Thu, 25 Mar 2021 07:50:33 +1100 (AEDT) [thread overview]
Message-ID: <b8ebab59-1cec-42d-6fb9-44aa1a464ae2@namei.org> (raw)
In-Reply-To: <20210322160253.4032422-4-arnd@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Mon, 22 Mar 2021, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> gcc-11 introdces a harmless warning for cap_inode_getsecurity:
>
> security/commoncap.c: In function ‘cap_inode_getsecurity’:
> security/commoncap.c:440:33: error: ‘memcpy’ reading 16 bytes from a region of size 0 [-Werror=stringop-overread]
> 440 | memcpy(&nscap->data, &cap->data, sizeof(__le32) * 2 * VFS_CAP_U32);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The problem here is that tmpbuf is initialized to NULL, so gcc assumes
> it is not accessible unless it gets set by vfs_getxattr_alloc(). This is
> a legitimate warning as far as I can tell, but the code is correct since
> it correctly handles the error when that function fails.
>
> Add a separate NULL check to tell gcc about it as well.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git fixes-v5.12
--
James Morris
<jmorris@namei.org>
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris@namei.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: dri-devel@lists.freedesktop.org,
Christian Brauner <christian.brauner@ubuntu.com>,
linux-scsi@vger.kernel.org, x86@kernel.org,
James Smart <james.smart@broadcom.com>,
tboot-devel@lists.sourceforge.net,
Kalle Valo <kvalo@codeaurora.org>,
ath11k@lists.infradead.org, Serge Hallyn <serge@hallyn.com>,
Miklos Szeredi <mszeredi@redhat.com>,
Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Ning Sun <ning.sun@intel.com>, Anders Larsen <al@alarsen.net>,
cgroups@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Martin Sebor <msebor@gcc.gnu.org>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Tejun Heo <tj@kernel.org>, Simon Kelley <simon@thekelleys.org.uk>,
intel-gfx@lists.freedesktop.org,
Tycho Andersen <tycho@tycho.pizza>
Subject: Re: [PATCH 03/11] security: commoncap: fix -Wstringop-overread warning
Date: Thu, 25 Mar 2021 07:50:33 +1100 (AEDT) [thread overview]
Message-ID: <b8ebab59-1cec-42d-6fb9-44aa1a464ae2@namei.org> (raw)
In-Reply-To: <20210322160253.4032422-4-arnd@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Mon, 22 Mar 2021, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> gcc-11 introdces a harmless warning for cap_inode_getsecurity:
>
> security/commoncap.c: In function ‘cap_inode_getsecurity’:
> security/commoncap.c:440:33: error: ‘memcpy’ reading 16 bytes from a region of size 0 [-Werror=stringop-overread]
> 440 | memcpy(&nscap->data, &cap->data, sizeof(__le32) * 2 * VFS_CAP_U32);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The problem here is that tmpbuf is initialized to NULL, so gcc assumes
> it is not accessible unless it gets set by vfs_getxattr_alloc(). This is
> a legitimate warning as far as I can tell, but the code is correct since
> it correctly handles the error when that function fails.
>
> Add a separate NULL check to tell gcc about it as well.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git fixes-v5.12
--
James Morris
<jmorris@namei.org>
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris@namei.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: dri-devel@lists.freedesktop.org,
Christian Brauner <christian.brauner@ubuntu.com>,
linux-scsi@vger.kernel.org, x86@kernel.org,
James Smart <james.smart@broadcom.com>,
tboot-devel@lists.sourceforge.net,
Kalle Valo <kvalo@codeaurora.org>,
ath11k@lists.infradead.org, Serge Hallyn <serge@hallyn.com>,
Miklos Szeredi <mszeredi@redhat.com>,
Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Ning Sun <ning.sun@intel.com>, Anders Larsen <al@alarsen.net>,
cgroups@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Martin Sebor <msebor@gcc.gnu.org>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Tejun Heo <tj@kernel.org>, Simon Kelley <simon@thekelleys.org.uk>,
intel-gfx@lists.freedesktop.org,
Tycho Andersen <tycho@tycho.pizza>
Subject: Re: [Intel-gfx] [PATCH 03/11] security: commoncap: fix -Wstringop-overread warning
Date: Thu, 25 Mar 2021 07:50:33 +1100 (AEDT) [thread overview]
Message-ID: <b8ebab59-1cec-42d-6fb9-44aa1a464ae2@namei.org> (raw)
In-Reply-To: <20210322160253.4032422-4-arnd@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Mon, 22 Mar 2021, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> gcc-11 introdces a harmless warning for cap_inode_getsecurity:
>
> security/commoncap.c: In function ‘cap_inode_getsecurity’:
> security/commoncap.c:440:33: error: ‘memcpy’ reading 16 bytes from a region of size 0 [-Werror=stringop-overread]
> 440 | memcpy(&nscap->data, &cap->data, sizeof(__le32) * 2 * VFS_CAP_U32);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The problem here is that tmpbuf is initialized to NULL, so gcc assumes
> it is not accessible unless it gets set by vfs_getxattr_alloc(). This is
> a legitimate warning as far as I can tell, but the code is correct since
> it correctly handles the error when that function fails.
>
> Add a separate NULL check to tell gcc about it as well.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git fixes-v5.12
--
James Morris
<jmorris@namei.org>
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
To: Arnd Bergmann <arnd-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Martin Sebor <msebor-/MQLu3FmUzdAfugRpC6u6w@public.gmane.org>,
Serge Hallyn <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
Ning Sun <ning.sun-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Jani Nikula <jani.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Simon Kelley
<simon-xn1N/tgparsycpQjotevgVpr/1R2p/CL@public.gmane.org>,
James Smart <james.smart-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
"James E.J. Bottomley"
<jejb-tEXmvtCZX7AybS5Ee8rs3A@public.gmane.org>,
Anders Larsen <al-V9/YLgxv/GvR7s880joybQ@public.gmane.org>,
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Imre Deak <imre.deak-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
tboot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
intel-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
ath11k-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-security-module-fy+rA21nqHI@public.gmane.org
Subject: Re: [PATCH 03/11] security: commoncap: fix -Wstringop-overread warning
Date: Thu, 25 Mar 2021 07:50:33 +1100 (AEDT) [thread overview]
Message-ID: <b8ebab59-1cec-42d-6fb9-44aa1a464ae2@namei.org> (raw)
In-Reply-To: <20210322160253.4032422-4-arnd-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On Mon, 22 Mar 2021, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
>
> gcc-11 introdces a harmless warning for cap_inode_getsecurity:
>
> security/commoncap.c: In function ‘cap_inode_getsecurity’:
> security/commoncap.c:440:33: error: ‘memcpy’ reading 16 bytes from a region of size 0 [-Werror=stringop-overread]
> 440 | memcpy(&nscap->data, &cap->data, sizeof(__le32) * 2 * VFS_CAP_U32);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The problem here is that tmpbuf is initialized to NULL, so gcc assumes
> it is not accessible unless it gets set by vfs_getxattr_alloc(). This is
> a legitimate warning as far as I can tell, but the code is correct since
> it correctly handles the error when that function fails.
>
> Add a separate NULL check to tell gcc about it as well.
>
> Signed-off-by: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git fixes-v5.12
--
James Morris
<jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
next prev parent reply other threads:[~2021-03-24 20:57 UTC|newest]
Thread overview: 197+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 16:02 [PATCH 00/11] treewide: address gcc-11 -Wstringop-overread warnings Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [PATCH 01/11] x86: compressed: avoid gcc-11 -Wstringop-overread warning Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 23:30 ` [tip: x86/boot] x86/boot/compressed: Avoid " tip-bot2 for Arnd Bergmann
2021-03-22 16:02 ` [PATCH 02/11] x86: tboot: avoid Wstringop-overread-warning Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 20:29 ` Ingo Molnar
2021-03-22 20:29 ` Ingo Molnar
2021-03-22 20:29 ` [Intel-gfx] " Ingo Molnar
2021-03-22 20:29 ` Ingo Molnar
2021-03-22 20:29 ` Ingo Molnar
2021-03-22 20:29 ` Ingo Molnar
2021-03-22 21:39 ` Arnd Bergmann
2021-03-22 21:39 ` Arnd Bergmann
2021-03-22 21:39 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 21:39 ` Arnd Bergmann
2021-03-22 21:39 ` Arnd Bergmann
2021-03-22 21:39 ` Arnd Bergmann
2021-03-22 22:07 ` Martin Sebor
2021-03-22 22:07 ` Martin Sebor
2021-03-22 22:07 ` [Intel-gfx] " Martin Sebor
2021-03-22 22:07 ` Martin Sebor
2021-03-22 22:07 ` Martin Sebor
2021-03-22 22:07 ` Martin Sebor
2021-03-22 22:49 ` Arnd Bergmann
2021-03-22 22:49 ` Arnd Bergmann
2021-03-22 22:49 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 22:49 ` Arnd Bergmann
2021-03-22 22:49 ` Arnd Bergmann
2021-03-22 22:49 ` Arnd Bergmann
2021-03-22 23:13 ` Ingo Molnar
2021-03-22 23:13 ` Ingo Molnar
2021-03-22 23:13 ` [Intel-gfx] " Ingo Molnar
2021-03-22 23:13 ` Ingo Molnar
2021-03-22 23:13 ` Ingo Molnar
2021-03-22 23:13 ` Ingo Molnar
2021-03-24 9:11 ` David Laight
2021-03-24 9:11 ` David Laight
2021-03-24 9:11 ` [Intel-gfx] " David Laight
2021-03-24 9:11 ` David Laight
2021-03-24 9:11 ` David Laight
2021-03-24 9:11 ` David Laight
2021-03-24 10:39 ` David Laight
2021-03-24 10:39 ` David Laight
2021-03-24 10:39 ` [Intel-gfx] " David Laight
2021-03-24 10:39 ` David Laight
2021-03-24 10:39 ` David Laight
2021-03-24 10:39 ` David Laight
2021-03-22 23:30 ` [tip: x86/boot] x86/boot/tboot: Avoid Wstringop-overread-warning tip-bot2 for Arnd Bergmann
2021-03-22 16:02 ` [PATCH 03/11] security: commoncap: fix -Wstringop-overread warning Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:31 ` Christian Brauner
2021-03-22 16:31 ` Christian Brauner
2021-03-22 16:31 ` [Intel-gfx] " Christian Brauner
2021-03-22 16:31 ` Christian Brauner
2021-03-22 16:31 ` Christian Brauner
2021-03-22 16:31 ` Christian Brauner
2021-03-24 20:50 ` James Morris [this message]
2021-03-24 20:50 ` James Morris
2021-03-24 20:50 ` [Intel-gfx] " James Morris
2021-03-24 20:50 ` James Morris
2021-03-24 20:50 ` James Morris
2021-03-24 20:50 ` James Morris
2021-03-22 16:02 ` [PATCH 04/11] ath11: Wstringop-overread warning Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-09-28 9:04 ` Kalle Valo
2021-09-28 9:04 ` Kalle Valo
2021-09-28 9:04 ` Kalle Valo
2021-09-28 9:04 ` Kalle Valo
2021-09-28 9:04 ` Kalle Valo
2021-09-28 9:04 ` [Intel-gfx] " Kalle Valo
2021-03-22 16:02 ` [PATCH 05/11] qnx: avoid -Wstringop-overread warning Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [PATCH 06/11] cgroup: fix -Wzero-length-bounds warnings Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-30 8:41 ` Michal Koutný
2021-03-30 8:41 ` Michal Koutný
2021-03-30 8:41 ` [Intel-gfx] " Michal Koutný
2021-03-30 8:41 ` Michal Koutný
2021-03-30 8:41 ` Michal Koutný
2021-03-30 8:41 ` Michal Koutný
2021-03-30 9:00 ` Arnd Bergmann
2021-03-30 9:00 ` Arnd Bergmann
2021-03-30 9:00 ` [Intel-gfx] " Arnd Bergmann
2021-03-30 9:00 ` Arnd Bergmann
2021-03-30 9:00 ` Arnd Bergmann
2021-03-30 9:00 ` Arnd Bergmann
2021-03-30 14:44 ` Michal Koutný
2021-03-30 14:44 ` Michal Koutný
2021-03-30 14:44 ` [Intel-gfx] " Michal Koutný
2021-03-30 14:44 ` Michal Koutný
2021-03-30 14:44 ` Michal Koutný
2021-03-30 14:44 ` Michal Koutný
2021-03-22 16:02 ` [PATCH 07/11] ARM: sharpsl_param: work around -Wstringop-overread warning Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [PATCH 08/11] atmel: avoid gcc -Wstringop-overflow warning Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [PATCH 09/11] scsi: lpfc: fix gcc -Wstringop-overread warning Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [PATCH 10/11] drm/i915: avoid stringop-overread warning on pri_latency Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-24 15:30 ` Jani Nikula
2021-03-24 15:30 ` Jani Nikula
2021-03-24 15:30 ` [Intel-gfx] " Jani Nikula
2021-03-24 15:30 ` Jani Nikula
2021-03-24 15:30 ` Jani Nikula
2021-03-24 15:30 ` Jani Nikula
2021-03-24 17:22 ` Ville Syrjälä
2021-03-24 17:22 ` Ville Syrjälä
2021-03-24 17:22 ` [Intel-gfx] " Ville Syrjälä
2021-03-24 17:22 ` Ville Syrjälä
2021-03-24 17:22 ` Ville Syrjälä
2021-03-24 17:22 ` Ville Syrjälä
2021-03-22 16:02 ` [PATCH 11/11] [RFC] drm/i915/dp: fix array overflow warning Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` [Intel-gfx] " Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-22 16:02 ` Arnd Bergmann
2021-03-25 8:05 ` Jani Nikula
2021-03-25 8:05 ` Jani Nikula
2021-03-25 8:05 ` [Intel-gfx] " Jani Nikula
2021-03-25 8:05 ` Jani Nikula
2021-03-25 8:05 ` Jani Nikula
2021-03-25 8:05 ` Jani Nikula
2021-03-25 9:53 ` Arnd Bergmann
2021-03-25 9:53 ` Arnd Bergmann
2021-03-25 9:53 ` [Intel-gfx] " Arnd Bergmann
2021-03-25 9:53 ` Arnd Bergmann
2021-03-25 9:53 ` Arnd Bergmann
2021-03-25 9:53 ` Arnd Bergmann
2021-03-25 14:49 ` Martin Sebor
2021-03-25 14:49 ` Martin Sebor
2021-03-25 14:49 ` [Intel-gfx] " Martin Sebor
2021-03-25 14:49 ` Martin Sebor
2021-03-25 14:49 ` Martin Sebor
2021-03-25 14:49 ` Martin Sebor
2021-03-30 10:56 ` Hans de Goede
2021-03-30 10:56 ` Hans de Goede
2021-03-30 10:56 ` [Intel-gfx] " Hans de Goede
2021-03-30 10:56 ` Hans de Goede
2021-03-30 10:56 ` Hans de Goede
2021-03-30 10:56 ` Hans de Goede
2021-03-22 19:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for treewide: address gcc-11 -Wstringop-overread warnings Patchwork
2021-03-22 19:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-03-22 19:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-03-23 15:30 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for treewide: address gcc-11 -Wstringop-overread warnings (rev2) Patchwork
2021-03-25 22:35 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for treewide: address gcc-11 -Wstringop-overread warnings (rev3) Patchwork
2021-03-30 11:50 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for treewide: address gcc-11 -Wstringop-overread warnings (rev4) Patchwork
2021-04-06 4:53 ` [PATCH 00/11] treewide: address gcc-11 -Wstringop-overread warnings Martin K. Petersen
2021-04-06 4:53 ` [Intel-gfx] " Martin K. Petersen
2021-04-06 4:53 ` Martin K. Petersen
2021-04-06 4:53 ` Martin K. Petersen
2021-04-06 4:53 ` Martin K. Petersen
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=b8ebab59-1cec-42d-6fb9-44aa1a464ae2@namei.org \
--to=jmorris@namei.org \
--cc=al@alarsen.net \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=cgroups@vger.kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ebiederm@xmission.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=james.smart@broadcom.com \
--cc=jani.nikula@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=keescook@chromium.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=msebor@gcc.gnu.org \
--cc=mszeredi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=ning.sun@intel.com \
--cc=serge@hallyn.com \
--cc=simon@thekelleys.org.uk \
--cc=tboot-devel@lists.sourceforge.net \
--cc=tj@kernel.org \
--cc=tycho@tycho.pizza \
--cc=x86@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.