From: Yonghong Song <yhs@fb.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: <bpf@vger.kernel.org>, Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH v4 bpf-next] selftests/bpf: Use the last page in test_snprintf_btf on s390
Date: Sun, 28 Feb 2021 20:30:39 -0800 [thread overview]
Message-ID: <405c1624-955c-ecee-7557-be7a0d2488fd@fb.com> (raw)
In-Reply-To: <20210227051726.121256-1-iii@linux.ibm.com>
On 2/26/21 9:17 PM, Ilya Leoshkevich wrote:
> test_snprintf_btf fails on s390, because NULL points to a readable
> struct lowcore there. Fix by using the last page instead.
>
> Error message example:
>
> printing fffffffffffff000 should generate error, got (361)
>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2021-03-01 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 5:17 [PATCH v4 bpf-next] selftests/bpf: Use the last page in test_snprintf_btf on s390 Ilya Leoshkevich
2021-02-28 8:06 ` Heiko Carstens
2021-03-01 4:30 ` Yonghong Song [this message]
2021-03-02 10:40 ` patchwork-bot+netdevbpf
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=405c1624-955c-ecee-7557-be7a0d2488fd@fb.com \
--to=yhs@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=iii@linux.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox