From: Michal Hocko <mhocko@suse.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Matthew Wilcox <willy@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <guro@fb.com>, Rik van Riel <riel@surriel.com>,
Minchan Kim <minchan@kernel.org>,
Christian Brauner <christian@brauner.io>,
Christoph Hellwig <hch@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
David Hildenbrand <david@redhat.com>,
Jann Horn <jannh@google.com>, Andy Lutomirski <luto@kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
Florian Weimer <fweimer@redhat.com>,
jengelh@inai.de, Tim Murray <timmurray@google.com>,
Linux API <linux-api@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-team <kernel-team@android.com>
Subject: Re: [PATCH v3 1/2] mm: introduce process_mrelease system call
Date: Mon, 26 Jul 2021 10:20:35 +0200 [thread overview]
Message-ID: <YP5wUxx/TflLP6dq@dhcp22.suse.cz> (raw)
In-Reply-To: <CALvZod7ehaHoWRD-Pzvet5c1LQ6DYDHjs=xbJWZYEdMsgTpRgA@mail.gmail.com>
On Thu 22-07-21 19:03:56, Shakeel Butt wrote:
> On Thu, Jul 22, 2021 at 6:14 PM Suren Baghdasaryan <surenb@google.com> wrote:
> >
> [...]
> > +
> > + mmap_read_lock(mm);
>
> How about mmap_read_trylock(mm) and return -EAGAIN on failure?
Btw. wether there is a non-blocking variant or not we should use
killable waiting to make sure the task calling into this is killable
by userspace (e.g. to implement a timeout based approach).
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2021-07-26 8:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 1:14 [PATCH v3 1/2] mm: introduce process_mrelease system call Suren Baghdasaryan
2021-07-23 1:14 ` Suren Baghdasaryan
2021-07-23 1:14 ` [PATCH v3 2/2] mm: wire up syscall process_mrelease Suren Baghdasaryan
2021-07-23 1:14 ` Suren Baghdasaryan
2021-07-23 2:03 ` [PATCH v3 1/2] mm: introduce process_mrelease system call Shakeel Butt
2021-07-23 2:03 ` Shakeel Butt
2021-07-23 4:47 ` Suren Baghdasaryan
2021-07-23 6:20 ` Michal Hocko
2021-07-23 8:11 ` Suren Baghdasaryan
2021-07-23 8:15 ` David Hildenbrand
2021-07-23 8:18 ` Suren Baghdasaryan
2021-07-23 8:18 ` Suren Baghdasaryan
2021-07-23 8:53 ` Michal Hocko
2021-07-23 13:46 ` Shakeel Butt
2021-07-23 13:46 ` Shakeel Butt
2021-07-23 16:08 ` Suren Baghdasaryan
2021-07-23 16:08 ` Suren Baghdasaryan
2021-07-23 17:00 ` Shakeel Butt
2021-07-23 17:00 ` Shakeel Butt
2021-07-26 7:27 ` Michal Hocko
2021-07-26 13:43 ` Shakeel Butt
2021-07-26 13:43 ` Shakeel Butt
2021-08-02 19:53 ` Suren Baghdasaryan
2021-08-02 19:53 ` Suren Baghdasaryan
2021-08-02 20:05 ` Shakeel Butt
2021-08-02 20:05 ` Shakeel Butt
2021-08-02 20:08 ` Suren Baghdasaryan
2021-08-02 20:08 ` Suren Baghdasaryan
2021-08-02 22:16 ` Suren Baghdasaryan
2021-08-02 22:16 ` Suren Baghdasaryan
2021-07-23 13:40 ` Shakeel Butt
2021-07-23 13:40 ` Shakeel Butt
2021-07-26 8:20 ` Michal Hocko [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=YP5wUxx/TflLP6dq@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=christian.brauner@ubuntu.com \
--cc=christian@brauner.io \
--cc=david@redhat.com \
--cc=fweimer@redhat.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=jannh@google.com \
--cc=jengelh@inai.de \
--cc=kernel-team@android.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=minchan@kernel.org \
--cc=oleg@redhat.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=surenb@google.com \
--cc=timmurray@google.com \
--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.