From: Conor Dooley <conor@kernel.org>
To: Eva Kotova <nyandarknessgirl@gmail.com>
Cc: PH7PR14MB559464DBDD310E755F5B21E8CEDC9@ph7pr14mb5594.namprd14.prod.outlook.com,
c141028@gmail.com, coelacanthus@outlook.com,
dramforever@live.com, linux-riscv@lists.infradead.org,
palmer@dabbelt.com, xc-tan@outlook.com
Subject: Re: [PATCH] riscv: mmap with PROT_WRITE but no PROT_READ is invalid
Date: Thu, 6 Oct 2022 21:03:07 +0100 [thread overview]
Message-ID: <Yz80ewHKTPI5Rvuz@spud> (raw)
In-Reply-To: <20282242-5cad-42be-ce6c-834b0e7ef269@gmail.com>
On Thu, Oct 06, 2022 at 10:55:00PM +0300, Eva Kotova wrote:
> Patch "[PATCH v4 2/2] riscv: Allow PROT_WRITE-only mmap()" applied cleanly
> over 5.19, fixed issues with OpenJDK.
>
> I assume this is not yet merged into linux-next, because problem persists
> there, hope this gets merged soon.
Yeah, not been applied yet. If you reply with a Tested-by that will help
though! Would be good to also note that it breaks userspace.
FYI, you've got an issue with your mail client, my msg-id from my last
mail (Yz8r71PjHlpLy+kR@spud) ended up as the reply-to address for this
one. The first email you sent tonight was fine though.
Thanks,
Conor.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-10-06 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 7:56 [PATCH] riscv: mmap with PROT_WRITE but no PROT_READ is invalid Celeste Liu
2022-07-21 23:19 ` Palmer Dabbelt
2022-10-06 19:17 ` Eva Kotova
2022-10-06 19:29 ` Conor Dooley
2022-10-11 11:23 ` Heinrich Schuchardt
2022-10-11 11:31 ` Coelacanthus
2022-10-06 19:20 ` Eva Kotova
2022-10-06 19:26 ` Conor Dooley
2022-10-06 19:55 ` Eva Kotova
2022-10-06 20:03 ` Conor Dooley [this message]
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=Yz80ewHKTPI5Rvuz@spud \
--to=conor@kernel.org \
--cc=PH7PR14MB559464DBDD310E755F5B21E8CEDC9@ph7pr14mb5594.namprd14.prod.outlook.com \
--cc=c141028@gmail.com \
--cc=coelacanthus@outlook.com \
--cc=dramforever@live.com \
--cc=linux-riscv@lists.infradead.org \
--cc=nyandarknessgirl@gmail.com \
--cc=palmer@dabbelt.com \
--cc=xc-tan@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.