From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Greg Thelen <gthelen@google.com>, Davidlohr Bueso <davidlohr@hp.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Manfred Spraul <manfred@colorfullife.com>,
aswin@hp.com, LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] ipc,shm: increase default size for shmmax
Date: Wed, 02 Apr 2014 10:58:24 +0900 [thread overview]
Message-ID: <533B6EC0.10303@jp.fujitsu.com> (raw)
In-Reply-To: <xr937g78k06y.fsf@gthelen.mtv.corp.google.com>
(2014/04/02 10:08), Greg Thelen wrote:
>
> On Tue, Apr 01 2014, Davidlohr Bueso <davidlohr@hp.com> wrote:
>
>> On Tue, 2014-04-01 at 19:56 -0400, KOSAKI Motohiro wrote:
>>>>>> Ah-hah, that's interesting info.
>>>>>>
>>>>>> Let's make the default 64GB?
>>>>>
>>>>> 64GB is infinity at that time, but it no longer near infinity today. I like
>>>>> very large or total memory proportional number.
>>>>
>>>> So I still like 0 for unlimited. Nice, clean and much easier to look at
>>>> than ULONG_MAX. And since we cannot disable shm through SHMMIN, I really
>>>> don't see any disadvantages, as opposed to some other arbitrary value.
>>>> Furthermore it wouldn't break userspace: any existing sysctl would
>>>> continue to work, and if not set, the user never has to worry about this
>>>> tunable again.
>>>>
>>>> Please let me know if you all agree with this...
>>>
>>> Surething. Why not. :)
>>
>> *sigh* actually, the plot thickens a bit with SHMALL (total size of shm
>> segments system wide, in pages). Currently by default:
>>
>> #define SHMALL (SHMMAX/getpagesize()*(SHMMNI/16))
>>
>> This deals with physical memory, at least admins are recommended to set
>> it to some large percentage of ram / pagesize. So I think that if we
>> loose control over the default value, users can potentially DoS the
>> system, or at least cause excessive swapping if not manually set, but
>> then again the same goes for anon mem... so do we care?
>
> At least when there's an egregious anon leak the oom killer has the
> power to free the memory by killing until the memory is unreferenced.
> This isn't true for shm or tmpfs. So shm is more effective than anon at
> crushing a machine.
Hm..sysctl.kernel.shm_rmid_forced won't work with oom-killer ?
http://www.openwall.com/lists/kernel-hardening/2011/07/26/7
I like to handle this kind of issue under memcg but hmm..tmpfs's limit is half
of memory at default.
Thanks,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-04-02 2:01 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 3:06 Davidlohr Bueso
2014-03-31 21:32 ` Andrew Morton
2014-03-31 22:59 ` Davidlohr Bueso
2014-03-31 23:13 ` Andrew Morton
2014-03-31 23:25 ` Davidlohr Bueso
2014-04-01 0:05 ` Andrew Morton
2014-04-01 6:29 ` Kamezawa Hiroyuki
2014-04-01 19:19 ` Andrew Morton
2014-04-01 20:15 ` KOSAKI Motohiro
2014-04-01 20:26 ` Davidlohr Bueso
2014-04-02 0:11 ` Kamezawa Hiroyuki
2014-04-02 1:02 ` Kamezawa Hiroyuki
2014-04-02 14:55 ` One Thousand Gnomes
2014-04-02 23:47 ` Kamezawa Hiroyuki
2014-04-01 17:01 ` Davidlohr Bueso
2014-04-01 18:10 ` KOSAKI Motohiro
2014-04-01 18:31 ` Davidlohr Bueso
2014-04-01 19:51 ` KOSAKI Motohiro
2014-04-01 21:01 ` Davidlohr Bueso
2014-04-01 21:12 ` KOSAKI Motohiro
2014-04-01 21:29 ` Andrew Morton
2014-04-01 21:41 ` KOSAKI Motohiro
2014-04-01 21:48 ` Andrew Morton
2014-04-01 22:02 ` Davidlohr Bueso
2014-04-01 22:08 ` Andrew Morton
2014-04-13 18:05 ` Manfred Spraul
2014-04-13 23:15 ` Davidlohr Bueso
2014-04-16 22:46 ` Andrew Morton
2014-04-16 23:19 ` Davidlohr Bueso
2014-04-17 10:41 ` Michael Kerrisk
2014-04-17 16:41 ` Manfred Spraul
2014-04-17 20:19 ` Michael Kerrisk (man-pages)
2014-04-01 22:49 ` KOSAKI Motohiro
2014-04-01 23:28 ` Davidlohr Bueso
2014-04-01 23:56 ` KOSAKI Motohiro
2014-04-02 0:40 ` Davidlohr Bueso
2014-04-02 1:08 ` Greg Thelen
2014-04-02 1:58 ` Kamezawa Hiroyuki [this message]
2014-04-02 2:11 ` Greg Thelen
2014-04-03 0:20 ` [PATCH] ipc,shm: disable shmmax and shmall by default Davidlohr Bueso
2014-04-03 14:07 ` Kamezawa Hiroyuki
2014-04-03 19:02 ` Manfred Spraul
2014-04-03 19:50 ` Davidlohr Bueso
2014-04-03 23:39 ` KOSAKI Motohiro
2014-04-04 5:00 ` Davidlohr Bueso
2014-04-05 18:24 ` KOSAKI Motohiro
2014-04-06 6:42 ` Manfred Spraul
2014-04-06 16:54 ` Davidlohr Bueso
2014-04-03 22:29 ` KOSAKI Motohiro
2014-04-03 23:47 ` KOSAKI Motohiro
2014-04-11 18:28 ` Manfred Spraul
2014-04-11 20:27 ` Davidlohr Bueso
2014-04-11 20:48 ` Davidlohr Bueso
2014-04-12 8:50 ` Manfred Spraul
2014-04-12 15:33 ` Davidlohr Bueso
2014-04-01 21:43 ` [PATCH] ipc,shm: increase default size for shmmax Davidlohr Bueso
2014-04-01 19:26 ` Andrew Morton
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=533B6EC0.10303@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=gthelen@google.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox