From: Ricardo Biehl Pasquali <pasqualirb@gmail.com>
To: perex@perex.cz
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v6 0/3] ALSA: pcm: anonymous dup implementation
Date: Tue, 5 Feb 2019 16:24:45 -0200 [thread overview]
Message-ID: <20190205182444.GA20812@localhost.localdomain> (raw)
What about file sealing?
See:
Jonathan Corbet's article about sealed files (2014-04-09).
<https://lwn.net/Articles/593918/>.
Theodore Ts'o reply to file sealing patch suggesting an
implementation on VFS (2014-03-20).
Re: [PATCH 0/6] File Sealing & memfd_create()
<https://lwn.net/Articles/593963/>.
pasquali
next reply other threads:[~2019-02-05 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 18:24 Ricardo Biehl Pasquali [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-04 18:38 [PATCH v6 0/3] ALSA: pcm: anonymous dup implementation Jaroslav Kysela
2019-02-07 16:29 ` Mark Brown
2019-02-08 16:14 ` Takashi Iwai
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=20190205182444.GA20812@localhost.localdomain \
--to=pasqualirb@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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