On 23.08.2021 08:00, Abdul Haleem wrote:
> Greeting's
>
> Todays net-next branch fails to build on my powerpc box with below error
>
> CC [M] drivers/gpu/drm/virtio/virtgpu_trace_points.o
> CC [M] drivers/net/ethernet/atheros/atl1e/atl1e_ethtool.o
> drivers/net/ethernet/broadcom/bnx2x/bnx2x
On Sat, Aug 21, 2021 at 02:54:17PM +0530, Srikar Dronamraju wrote:
> Aneesh reported a crash with a fairly recent upstream kernel when
> booting kernel whose commandline was appended with nr_cpus=2
>
> 1:mon> e
> cpu 0x1: Vector: 300 (Data Access) at [c8a67bd0]
> pc: c002557c:
Kees Cook writes:
> On Fri, Aug 20, 2021 at 05:49:35PM +1000, Michael Ellerman wrote:
>> Kees Cook writes:
>> > In preparation for FORTIFY_SOURCE performing compile-time and run-time
>> > field bounds checking for memset(), avoid intentionally writing across
>> > neighboring fields.
>> >
>> > Add
On 4/14/21 12:00 PM, Jisheng Zhang wrote:
Many architectures implement the trap_init() as NOP, since there is
no such default for trap_init(), this empty stub is duplicated among
these architectures. Provide a generic but weak NOP implementation
to drop the empty stubs of trap_init() in these arc
The pull request you sent on Sun, 22 Aug 2021 09:53:18 +1000:
> https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
> tags/powerpc-5.14-6
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1bdc3d5be7e199ff56f39dafb0e5f63a9b8c975d
Thank you!
--
Deet-doot-d
allmodconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a005-20210822
powerpc allnoconfig
x86_64 randconfig-a005-20210822
x86_64 randconfig-a006-20210822
x86_64 randconfig-a001-20210822
x86_64 randconfig-a003-20210822
x86_64 randconfig-a004-20210822
x86_64
In preparation for FORTIFY_SOURCE performing compile-time and run-time
field bounds checking for memset(), avoid intentionally writing across
neighboring fields.
Instead of writing beyond the end of evt_struct->iu.srp.cmd, target the
upper union (evt_struct->iu.srp) instead, as that's what is bein
In preparation for FORTIFY_SOURCE performing compile-time and run-time
field bounds checking for memset(), avoid intentionally writing across
neighboring fields.
Instead of writing across a field boundary with memset(), move the call
to just the array, and an explicit zeroing of the prior field.