[syzbot] [bpf?] [trace?] KASAN: slab-use-after-free Read in bpf_trace_run1

Hello, syzbot found the following issue on: HEAD commit:520fad2e3206 selftests/bpf: scale benchmark counting by us.. git tree: bpf-next console+strace: https://syzkaller.appspot.com/x/log.txt?x=105af94618 kernel config: https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440 das

[PATCH 2/2] ARM: dts: qcom: Add support for Motorola Moto G (2013)

Add a device tree for the Motorola Moto G (2013) smartphone based on the Qualcomm MSM8226 SoC. Initially supported features: - Buttons (Volume Down/Up, Power) - eMMC - Hall Effect Sensor - SimpleFB display - TMP108 temperature sensor - Vibrator Signed-off-by: Stanislav Jakubek --- a

[PATCH 1/2] dt-bindings: arm: qcom: Add Motorola Moto G (2013)

Document the Motorola Moto G (2013), which is a smartphone based on the Qualcomm MSM8226 SoC. Signed-off-by: Stanislav Jakubek --- Documentation/devicetree/bindings/arm/qcom.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/

Re: [v2] ice: Fix freeing uninitialized pointers

>>> Automatically cleaned up pointers need to be initialized before exiting >>> their scope. In this case, they need to be initialized to NULL before >>> any return statement. >> >> * May we expect that compilers should report that affected variables >> were only declared here instead of appropr

Re: [PATCH v2 net] ice: Fix freeing uninitialized pointers

On Sat, Mar 23, 2024 at 05:56:29PM +0100, Markus Elfring wrote: > > Automatically cleaned up pointers need to be initialized before exiting > > their scope. In this case, they need to be initialized to NULL before > > any return statement. > > * May we expect that compilers should report that aff