mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alessandro Astone <ales.astone@gmail.com>
To: akpm@linux-foundation.org
Cc: kamezawa.hiroyu@jp.fujitsu.com, hughd@google.com,
	jakub@redhat.com, ales.astone@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Increasing the vm.max_map_count value
Date: Tue, 23 May 2023 16:15:54 +0200	[thread overview]
Message-ID: <a2b2c557-c46e-6236-24a1-d605758e87f2@gmail.com> (raw)

We are seeing userspace requiring more than the default 65330 mappings,
specifically some Windows games running through wine. We are looking into
changing the default in Fedora, but the source code includes a scary comment
about the current value:

 > Default maximum number of active map areas, this limits the number of 
vmas
 > per mm struct. Users can overwrite this number by sysctl but there is a
 > problem.
 >
 > When a program's coredump is generated as ELF format, a section is 
created
 > per a vma. In ELF, the number of sections is represented in unsigned 
short.
 > This means the number of sections should be smaller than 65535 at 
coredump.
 > Because the kernel adds some informative sections to a image of 
program at
 > generating coredump, we need some margin. The number of extra sections is
 > 1-3 now and depends on arch. We use "5" as safe margin, here.

It seems that going over 16 bits would at least break ELF coredumps (for
programs actually requesting as many mappings).

Do you think it is otherwise safe to increase this value arbitrarily?


                 reply	other threads:[~2023-05-23 14:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a2b2c557-c46e-6236-24a1-d605758e87f2@gmail.com \
    --to=ales.astone@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=jakub@redhat.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®