From: John Stultz <john.stultz@linaro.org>
To: Kay Sievers <kay@vrfy.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Greg KH <gregkh@linuxfoundation.org>,
Android Kernel Team <kernel-team@android.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Rik van Riel <riel@redhat.com>,
Michel Lespinasse <walken@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Neil Brown <neilb@suse.de>,
Andrea Arcangeli <aarcange@redhat.com>,
Takahiro Akashi <takahiro.akashi@linaro.org>,
Minchan Kim <minchan@kernel.org>,
Lennart Poettering <mzxreary@0pointer.de>
Subject: Re: [RFC] shmgetfd idea
Date: Tue, 28 Jan 2014 11:47:15 -0800 [thread overview]
Message-ID: <52E80943.3060806@linaro.org> (raw)
In-Reply-To: <CAPXgP10j5MVwhbkhOqx2z4SX-zAniNbZmk6jcK74Y_kMSN4SOA@mail.gmail.com>
On 01/27/2014 05:53 PM, Kay Sievers wrote:
> On Tue, Jan 28, 2014 at 2:37 AM, John Stultz <john.stultz@linaro.org> wrote:
>> Anyway, I just wanted to submit this sketched out idea as food for
>> thought to see if there was any objection or interest (I've got a draft
>> patch I'll send out once I get a chance to test it). So let me know if
>> you have any feedback or comments.
> The reason "kdbus-memfd" exists is primarily the sealing.
[snip]
> It would be nice if we can generalize the whole memfd logic, but the
> shmem allocation facility alone, without the sealing function cannot
> replace kdbus-memfd.
Yes. Quite understood. And I too hope to discuss how the sealing feature
could be generalized when the code is submitted for review. I just
figured I'd start here, so when that time comes we have a sketch for
what the rest of the parts that would be needed are.
> We would need secure sealing right from the start for the kdbus use
> case; other than that, there are no specific requirements from the
> kdbus side.
Thanks for the clarifications!
-john
--
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-01-28 19:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 1:37 [RFC] shmgetfd idea John Stultz
2014-01-28 1:53 ` Kay Sievers
2014-01-28 19:47 ` John Stultz [this message]
2014-01-28 3:52 ` H. Peter Anvin
2014-01-28 19:56 ` John Stultz
2014-01-28 20:37 ` H. Peter Anvin
2014-01-28 20:58 ` John Stultz
2014-01-28 21:01 ` Kay Sievers
2014-01-28 21:05 ` John Stultz
2014-01-28 21:10 ` H. Peter Anvin
2014-01-28 21:54 ` John Stultz
2014-01-28 22:14 ` Kay Sievers
2014-01-28 23:02 ` H. Peter Anvin
2014-01-28 23:14 ` Kay Sievers
2014-01-28 23:19 ` H. Peter Anvin
2014-01-29 0:14 ` Kay Sievers
2014-01-29 0:20 ` H. Peter Anvin
2014-01-29 0:49 ` Kay Sievers
2014-01-28 23:14 ` John Stultz
2014-01-28 21:28 ` Kay Sievers
2014-01-30 8:46 ` Christoph Hellwig
2014-01-30 16:02 ` Kay Sievers
2014-01-30 21:42 ` John Stultz
2014-01-31 0:01 ` Kay Sievers
2014-02-03 15:03 ` Christoph Hellwig
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=52E80943.3060806@linaro.org \
--to=john.stultz@linaro.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=hpa@linux.intel.com \
--cc=hughd@google.com \
--cc=kay@vrfy.org \
--cc=kernel-team@android.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mzxreary@0pointer.de \
--cc=neilb@suse.de \
--cc=riel@redhat.com \
--cc=takahiro.akashi@linaro.org \
--cc=walken@google.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;
as well as URLs for NNTP newsgroup(s).