linux-kernel - Re: [PATCH bpf-next] selftests/bpf: Sanitize pointer prior fclose()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <174249243205.1852962.16150935978028407496.git-patchwork-notify@kernel.org>
Date: Thu, 20 Mar 2025 17:40:32 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Björn Töpel <bjorn@...nel.org>@codeaurora.org
Cc: andrii@...nel.org, eddyz87@...il.com, mykolal@...com, bpf@...r.kernel.org,
 bjorn@...osinc.com, linux-kselftest@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Sanitize pointer prior fclose()

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:

On Tue, 18 Mar 2025 09:16:47 +0100 you wrote:
> From: Björn Töpel <bjorn@...osinc.com>
> 
> There are scenarios where env.{sub,}test_state->stdout_saved, can be
> NULL, e.g. sometimes when the watchdog timeout kicks in, or if the
> open_memstream syscall is not available.
> 
> Avoid crashing test_progs by adding an explicit NULL check prior the
> fclose() call.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Sanitize pointer prior fclose()
    https://git.kernel.org/bpf/bpf-next/c/e16e64f9e076

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html