From: Greg KH <gregkh@linuxfoundation.org>
To: Vivian Wang <wangruikang@iscas.ac.cn>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Inochi Amaoto <inochiama@gmail.com>,
Charlie Jenkins <charlie@rivosinc.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Yangyu Chen <cyy@cyyself.name>,
Palmer Dabbelt <palmer@dabbelt.com>,
Han Gao <rabenda.cn@gmail.com>, Paul Walmsley <pjw@kernel.org>,
linux-riscv@lists.infradead.org, Yao Zi <ziyao@disroot.org>
Subject: Re: riscv: Backport request for mmap address space fixes to 6.6
Date: Wed, 17 Sep 2025 14:34:15 +0200 [thread overview]
Message-ID: <2025091739-roundish-dropper-c4f6@gregkh> (raw)
In-Reply-To: <b68478db-5a8c-4b5f-a4d1-f4202ca1f062@iscas.ac.cn>
On Wed, Sep 17, 2025 at 08:03:08PM +0800, Vivian Wang wrote:
> Hi,
>
> I would like to request backport of these two commits to 6.6.y:
>
> b5b4287accd702f562a49a60b10dbfaf7d40270f ("riscv: mm: Use hint address in mmap if available")
> 2116988d5372aec51f8c4fb85bf8e305ecda47a0 ("riscv: mm: Do not restrict mmap address based on hint")
>
> Together, they amount to disabling arch_get_mmap_end and
> arch_get_mmap_base for riscv.
>
> I would like to note that the first patch conflicts with commit
> 724103429a2d ("riscv: mm: Fixup compat arch_get_mmap_end") in the stable
> linux-6.6.y branch. STACK_TOP_MAX should end up as TASK_SIZE, *not*
> TASK_SIZE_64.
Please submit a backported set of patches that you have properly fixed
up and tested to ensure that we get the backport correct, and we will be
glad to take them.
thanks,
greg k-h
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-09-17 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 12:03 riscv: Backport request for mmap address space fixes to 6.6 Vivian Wang
2025-09-17 12:34 ` Greg KH [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=2025091739-roundish-dropper-c4f6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cyy@cyyself.name \
--cc=inochiama@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=stable@vger.kernel.org \
--cc=wangruikang@iscas.ac.cn \
--cc=ziyao@disroot.org \
/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