linux-kernel - Re: [PATCH] mm-move-mremap-from-file_operations-to-vm_operations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <x49h9oysyct.fsf@segfault.boston.devel.redhat.com>
Date:	Mon, 20 Jul 2015 10:22:10 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Benjamin LaHaise <bcrl@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Joonsoo Kim <js1304@...il.com>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Johannes Weiner <hannes@...xchg.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm-move-mremap-from-file_operations-to-vm_operations_struct-fix

Hi, Oleg,

Oleg Nesterov <oleg@...hat.com> writes:

> Shouldn't we account aio events/pages somehow, say per-user, or in
> mm->pinned_vm ?

Ages ago I wrote a patch to account the completion ring to a process'
memlock limit:
  "[patch] aio: remove aio-max-nr and instead use the memlock rlimit to
   limit the number of pages pinned for the aio completion ring"
  http://marc.info/?l=linux-aio&m=123661380807041&w=2

The problem with that patch is that it modifies the user/kernel
interface.  It could be done over time, as Andrew outlined in that
thread, but I've been reluctant to take that on.

If you just mean we should account the memory so that the right process
can be killed, that sounds like a good idea to me.

Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/