All of lore.kernel.org
 help / color / mirror / Atom feed
From: Usama Arif <usama.arif@linux.dev>
To: Lance Yang <lance.yang@linux.dev>,
	r@hev.cc, Ryan Roberts <ryan.roberts@arm.com>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, david@kernel.org,
	jack@suse.cz, kees@kernel.org, willy@infradead.org,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, baolin.wang@linux.alibaba.com
Subject: Re: [PATCH v5] binfmt_elf: Align eligible read-only PT_LOAD segments to PMD_SIZE for THP
Date: Sun, 15 Mar 2026 16:12:02 +0300	[thread overview]
Message-ID: <0c2bd25d-1577-4935-8ebe-0762b480abfc@linux.dev> (raw)
In-Reply-To: <20260315034647.8462-1-lance.yang@linux.dev>



On 15/03/2026 06:46, Lance Yang wrote:
> Hi Rui,
> 
> CC Baolin and Usama
> 
> It would be better to keep earlier CC list across revisions, especially
> for people who have already reviewed or were explicitly include before.
> Otherwise, they may simply never see subsequent revisions, and from
> their side the discussion just stops there ...
> 
> Thanks,
> Lance
> 
Thanks! Also adding Ryan who did the exec_folio_order() work for ARM,
and also raised good concerns in [1]

The problem is not just alignment for elf, we need to fix more things like
mmap heuristics [2] and how unmapped areas are gotten [3].

[1] https://lore.kernel.org/all/cfdfca9c-4752-4037-a289-03e6e7a00d47@arm.com/
[2] https://lore.kernel.org/all/20260310145406.3073394-3-usama.arif@linux.dev/
[3] https://lore.kernel.org/all/20260310145406.3073394-5-usama.arif@linux.dev/


  parent reply	other threads:[~2026-03-15 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13  0:52 [PATCH v5] binfmt_elf: Align eligible read-only PT_LOAD segments to PMD_SIZE for THP WANG Rui
2026-03-15  3:46 ` Lance Yang
2026-03-15  4:10   ` WANG Rui
2026-03-15 13:12   ` Usama Arif [this message]
2026-03-20 11:44     ` David Hildenbrand (Arm)
2026-03-20 17:11       ` WANG Rui
2026-03-21 14:21         ` WANG Rui

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=0c2bd25d-1577-4935-8ebe-0762b480abfc@linux.dev \
    --to=usama.arif@linux.dev \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=brauner@kernel.org \
    --cc=david@kernel.org \
    --cc=jack@suse.cz \
    --cc=kees@kernel.org \
    --cc=lance.yang@linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=r@hev.cc \
    --cc=ryan.roberts@arm.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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 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.