From: "Mickaël Salaün" <mic@digikod.net>
To: linux-kernel@vger.kernel.org
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Jeff Dike" <jdike@addtoit.com>,
"Richard Weinberger" <richard@nod.at>,
"Tristan Schmelcher" <tschmelcher@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net
Subject: [PATCH v4 0/2] um: Protect memory mapped file
Date: Sat, 19 Dec 2015 19:18:29 +0100 [thread overview]
Message-ID: <1450549111-1297-1-git-send-email-mic@digikod.net> (raw)
This series protect the memory mapped file.
Changes since v3:
* add Tristan Schmelcher's ack
Changes since v2; addressed Tristan Schmelcher's comment:
* remove the whole fchmod call [1/2]
Changes since v1; addressed Richard Weinberger's comments:
* add attacker model to the patch description [1/2]
* remove errno reset [2/2]
Regards,
Mickaël
Mickaël Salaün (2):
um: Do not set unsecure permission for temporary file
um: Use race-free temporary file creation
arch/um/os-Linux/mem.c | 17 +++++++++++------
1 file changed, 11 insertions(+), 6 deletions(-)
--
2.6.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2015-12-19 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 18:18 Mickaël Salaün [this message]
2015-12-19 18:18 ` [PATCH v4 1/2] um: Do not set unsecure permission for temporary file Mickaël Salaün
2015-12-19 18:18 ` [PATCH v4 2/2] um: Use race-free temporary file creation Mickaël Salaün
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=1450549111-1297-1-git-send-email-mic@digikod.net \
--to=mic@digikod.net \
--cc=gregkh@linuxfoundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=tschmelcher@google.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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).