From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] mode_t whack-a-mole...
Date: Tue, 21 Nov 2017 23:56:31 +0000 [thread overview]
Message-ID: <20171121235631.GY21978@ZenIV.linux.org.uk> (raw)
For all internal uses we want umode_t, which is arch-independent;
mode_t (or __kernel_mode_t, for that matter) is wrong outside of userland
ABI. Unfortunately, that crap keeps coming back and needs to be put down
from time to time...
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.whack-a-mole
for you to fetch changes up to c6eb50d2790478d8b5841379b9502812a5e5feb3:
mode_t whack-a-mole: task_dump_owner() (2017-09-30 14:45:42 -0400)
----------------------------------------------------------------
Al Viro (1):
mode_t whack-a-mole: task_dump_owner()
fs/proc/base.c | 2 +-
fs/proc/internal.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
reply other threads:[~2017-11-21 23:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171121235631.GY21978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox