From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] mlock_8-1, munlock_10-1: don't use LONG_MAX as invalid pointer
Date: Wed, 20 Jan 2021 04:32:59 -0500 (EST) [thread overview]
Message-ID: <1542162728.33692863.1611135179166.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAEemH2dj2KGi6dmYoJaxsvvG1wvecbM8GrpBshHh8CTkm7pe+A@mail.gmail.com>
----- Original Message -----
> Hi Jan,
>
> I propose to reorg this patch with review comments (maybe apply it after
> the new release).
>
> Any thought?
This has been fixed in kernel by:
597399d0cb91 ("arm64: tags: Preserve tags for addresses translated via TTBR1")
d0022c0ef29b ("arm64: memory: Add missing brackets to untagged_addr() macro")
I'd keep the test as is, maybe add comment with above commits as a hint for future.
next prev parent reply other threads:[~2021-01-20 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 12:42 [LTP] [PATCH] mlock_8-1, munlock_10-1: don't use LONG_MAX as invalid pointer Jan Stancek
2019-10-14 12:50 ` Cyril Hrubis
2019-10-18 13:37 ` Petr Vorel
2019-10-18 13:39 ` Jan Stancek
2019-10-18 13:46 ` Petr Vorel
2021-01-20 3:10 ` Li Wang
2021-01-20 9:32 ` Jan Stancek [this message]
2021-01-20 9:46 ` Li Wang
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=1542162728.33692863.1611135179166.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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