Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix the snprintf test
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <161980501003.20779.4607601411037423780.git-patchwork-notify@kernel.org>
Date:   Fri, 30 Apr 2021 17:50:10 +0000
References: <20210428152501.1024509-1-revest@chromium.org>
In-Reply-To: <20210428152501.1024509-1-revest@chromium.org>
To:     Florent Revest <revest@chromium.org>
Cc:     bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
        andrii@kernel.org, kpsingh@kernel.org, jackmanb@google.com,
        linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to bpf/bpf.git (refs/heads/master):

On Wed, 28 Apr 2021 17:25:01 +0200 you wrote:
> The BPF program for the snprintf selftest runs on all syscall entries.
> On busy multicore systems this can cause concurrency issues.
> 
> For example it was observed that sometimes the userspace part of the
> test reads "    4 0000" instead of "    4 000" (extra '0' at the end)
> which seems to happen just before snprintf on another core sets
> end[-1] = '\0'.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix the snprintf test
    https://git.kernel.org/bpf/bpf/c/f80f88f0e2f2

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