From: David Laight <David.Laight@ACULAB.COM>
To: 'Martin Sebor' <msebor@gmail.com>, Ingo Molnar <mingo@kernel.org>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Martin Sebor" <msebor@gcc.gnu.org>,
Ning Sun <ning.sun@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"x86@kernel.org" <x86@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
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>,
Serge Hallyn <serge@hallyn.com>, Imre Deak <imre.deak@intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"tboot-devel@lists.sourceforge.net"
<tboot-devel@lists.sourceforge.net>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Will Deacon <will@kernel.org>
Subject: RE: [PATCH 02/11] x86: tboot: avoid Wstringop-overread-warning
Date: Wed, 24 Mar 2021 09:11:55 +0000 [thread overview]
Message-ID: <0aa198a1dd904231bcc29454bf19a812@AcuMS.aculab.com> (raw)
In-Reply-To: <b944a853-0e4b-b767-0175-cc2c1edba759@gmail.com>
From: Martin Sebor
> Sent: 22 March 2021 22:08
...
> In GCC 11, all access warnings expect objects to be either declared
> or allocated. Pointers with constant values are taken to point to
> nothing valid (as Arnd mentioned above, this is to detect invalid
> accesses to members of structs at address zero).
>
> One possible solution to the known address problem is to extend GCC
> attributes address and io that pin an object to a hardwired address
> to all targets (at the moment they're supported on just one or two
> targets). I'm not sure this can still happen before GCC 11 releases
> sometime in April or May.
A different solution is to define a normal C external data item
and then assign a fixed address with an asm statement or in
the linker script.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
WARNING: multiple messages have this Message-ID (diff)
From: David Laight <David.Laight@ACULAB.COM>
To: 'Martin Sebor' <msebor@gmail.com>, Ingo Molnar <mingo@kernel.org>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Martin Sebor" <msebor@gcc.gnu.org>,
Ning Sun <ning.sun@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"x86@kernel.org" <x86@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
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>,
Serge Hallyn <serge@hallyn.com>, Imre Deak <imre.deak@intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"tboot-devel@lists.sourceforge.net"
<tboot-devel@lists.sourceforge.net>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Will Deacon <will@kernel.org>
Subject: RE: [PATCH 02/11] x86: tboot: avoid Wstringop-overread-warning
Date: Wed, 24 Mar 2021 09:11:55 +0000 [thread overview]
Message-ID: <0aa198a1dd904231bcc29454bf19a812@AcuMS.aculab.com> (raw)
In-Reply-To: <b944a853-0e4b-b767-0175-cc2c1edba759@gmail.com>
From: Martin Sebor
> Sent: 22 March 2021 22:08
...
> In GCC 11, all access warnings expect objects to be either declared
> or allocated. Pointers with constant values are taken to point to
> nothing valid (as Arnd mentioned above, this is to detect invalid
> accesses to members of structs at address zero).
>
> One possible solution to the known address problem is to extend GCC
> attributes address and io that pin an object to a hardwired address
> to all targets (at the moment they're supported on just one or two
> targets). I'm not sure this can still happen before GCC 11 releases
> sometime in April or May.
A different solution is to define a normal C external data item
and then assign a fixed address with an asm statement or in
the linker script.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: David Laight <David.Laight@ACULAB.COM>
To: 'Martin Sebor' <msebor@gmail.com>, Ingo Molnar <mingo@kernel.org>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Martin Sebor" <msebor@gcc.gnu.org>,
Ning Sun <ning.sun@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"x86@kernel.org" <x86@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
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>,
Serge Hallyn <serge@hallyn.com>, Imre Deak <imre.deak@intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"tboot-devel@lists.sourceforge.net"
<tboot-devel@lists.sourceforge.net>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Will Deacon <will@kernel.org>
Subject: RE: [PATCH 02/11] x86: tboot: avoid Wstringop-overread-warning
Date: Wed, 24 Mar 2021 09:11:55 +0000 [thread overview]
Message-ID: <0aa198a1dd904231bcc29454bf19a812@AcuMS.aculab.com> (raw)
In-Reply-To: <b944a853-0e4b-b767-0175-cc2c1edba759@gmail.com>
From: Martin Sebor
> Sent: 22 March 2021 22:08
...
> In GCC 11, all access warnings expect objects to be either declared
> or allocated. Pointers with constant values are taken to point to
> nothing valid (as Arnd mentioned above, this is to detect invalid
> accesses to members of structs at address zero).
>
> One possible solution to the known address problem is to extend GCC
> attributes address and io that pin an object to a hardwired address
> to all targets (at the moment they're supported on just one or two
> targets). I'm not sure this can still happen before GCC 11 releases
> sometime in April or May.
A different solution is to define a normal C external data item
and then assign a fixed address with an asm statement or in
the linker script.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
_______________________________________________
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: David Laight <David.Laight@ACULAB.COM>
To: 'Martin Sebor' <msebor@gmail.com>, Ingo Molnar <mingo@kernel.org>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"H. Peter Anvin" <hpa@zytor.com>, Will Deacon <will@kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
James Smart <james.smart@broadcom.com>,
"tboot-devel@lists.sourceforge.net"
<tboot-devel@lists.sourceforge.net>,
Ingo Molnar <mingo@redhat.com>, Kalle Valo <kvalo@codeaurora.org>,
"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>,
Serge Hallyn <serge@hallyn.com>, Arnd Bergmann <arnd@arndb.de>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Ning Sun <ning.sun@intel.com>, Anders Larsen <al@alarsen.net>,
Borislav Petkov <bp@alien8.de>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Martin Sebor <msebor@gcc.gnu.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
Tejun Heo <tj@kernel.org>, Simon Kelley <simon@thekelleys.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: RE: [PATCH 02/11] x86: tboot: avoid Wstringop-overread-warning
Date: Wed, 24 Mar 2021 09:11:55 +0000 [thread overview]
Message-ID: <0aa198a1dd904231bcc29454bf19a812@AcuMS.aculab.com> (raw)
In-Reply-To: <b944a853-0e4b-b767-0175-cc2c1edba759@gmail.com>
From: Martin Sebor
> Sent: 22 March 2021 22:08
...
> In GCC 11, all access warnings expect objects to be either declared
> or allocated. Pointers with constant values are taken to point to
> nothing valid (as Arnd mentioned above, this is to detect invalid
> accesses to members of structs at address zero).
>
> One possible solution to the known address problem is to extend GCC
> attributes address and io that pin an object to a hardwired address
> to all targets (at the moment they're supported on just one or two
> targets). I'm not sure this can still happen before GCC 11 releases
> sometime in April or May.
A different solution is to define a normal C external data item
and then assign a fixed address with an asm statement or in
the linker script.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
_______________________________________________
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: David Laight <David.Laight@ACULAB.COM>
To: 'Martin Sebor' <msebor@gmail.com>, Ingo Molnar <mingo@kernel.org>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"H. Peter Anvin" <hpa@zytor.com>, Will Deacon <will@kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
James Smart <james.smart@broadcom.com>,
"tboot-devel@lists.sourceforge.net"
<tboot-devel@lists.sourceforge.net>,
Ingo Molnar <mingo@redhat.com>, Kalle Valo <kvalo@codeaurora.org>,
"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>,
Serge Hallyn <serge@hallyn.com>, Arnd Bergmann <arnd@arndb.de>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Ning Sun <ning.sun@intel.com>, Anders Larsen <al@alarsen.net>,
Borislav Petkov <bp@alien8.de>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Martin Sebor <msebor@gcc.gnu.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
Tejun Heo <tj@kernel.org>, Simon Kelley <simon@thekelleys.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH 02/11] x86: tboot: avoid Wstringop-overread-warning
Date: Wed, 24 Mar 2021 09:11:55 +0000 [thread overview]
Message-ID: <0aa198a1dd904231bcc29454bf19a812@AcuMS.aculab.com> (raw)
In-Reply-To: <b944a853-0e4b-b767-0175-cc2c1edba759@gmail.com>
From: Martin Sebor
> Sent: 22 March 2021 22:08
...
> In GCC 11, all access warnings expect objects to be either declared
> or allocated. Pointers with constant values are taken to point to
> nothing valid (as Arnd mentioned above, this is to detect invalid
> accesses to members of structs at address zero).
>
> One possible solution to the known address problem is to extend GCC
> attributes address and io that pin an object to a hardwired address
> to all targets (at the moment they're supported on just one or two
> targets). I'm not sure this can still happen before GCC 11 releases
> sometime in April or May.
A different solution is to define a normal C external data item
and then assign a fixed address with an asm statement or in
the linker script.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
_______________________________________________
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: David Laight <David.Laight@ACULAB.COM>
To: 'Martin Sebor' <msebor@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Arnd Bergmann <arnd@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Martin Sebor <msebor@gcc.gnu.org>, Ning Sun <ning.sun@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"x86@kernel.org" <x86@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
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>,
Serge Hallyn <serge@hallyn.com>, Imre Deak <imre.deak@intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"tboot-devel@lists.sourceforge.net" <tboot-devel@lists.sourc>
Subject: RE: [PATCH 02/11] x86: tboot: avoid Wstringop-overread-warning
Date: Wed, 24 Mar 2021 09:11:55 +0000 [thread overview]
Message-ID: <0aa198a1dd904231bcc29454bf19a812@AcuMS.aculab.com> (raw)
In-Reply-To: <b944a853-0e4b-b767-0175-cc2c1edba759@gmail.com>
From: Martin Sebor
> Sent: 22 March 2021 22:08
...
> In GCC 11, all access warnings expect objects to be either declared
> or allocated. Pointers with constant values are taken to point to
> nothing valid (as Arnd mentioned above, this is to detect invalid
> accesses to members of structs at address zero).
>
> One possible solution to the known address problem is to extend GCC
> attributes address and io that pin an object to a hardwired address
> to all targets (at the moment they're supported on just one or two
> targets). I'm not sure this can still happen before GCC 11 releases
> sometime in April or May.
A different solution is to define a normal C external data item
and then assign a fixed address with an asm statement or in
the linker script.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2021-03-24 9:13 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 [this message]
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
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=0aa198a1dd904231bcc29454bf19a812@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=al@alarsen.net \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=baolu.lu@linux.intel.com \
--cc=bp@alien8.de \
--cc=cgroups@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hpa@zytor.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=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=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=msebor@gcc.gnu.org \
--cc=msebor@gmail.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=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=will@kernel.org \
--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.