From: "Richard W.M. Jones" <rjones@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, jmarchan@redhat.com,
keescook@chromium.org, koct9i@gmail.com, pierre@spotify.com,
tytso@mit.edu, mm-commits@vger.kernel.org, linux-mm@kvack.org
Subject: Re: + procfs-expose-umask-in-proc-pid-status.patch added to -mm tree
Date: Mon, 25 Apr 2016 13:12:19 +0100 [thread overview]
Message-ID: <20160425121219.GQ11600@redhat.com> (raw)
In-Reply-To: <20160425093155.GD23933@dhcp22.suse.cz>
On Mon, Apr 25, 2016 at 11:31:55AM +0200, Michal Hocko wrote:
> On Fri 22-04-16 13:54:36, Andrew Morton wrote:
> > From: "Richard W.M. Jones" <rjones@redhat.com>
> > Subject: procfs: expose umask in /proc/<PID>/status
> >
> > It's not possible to read the process umask without also modifying it,
> > which is what umask(2) does. A library cannot read umask safely,
> > especially if the main program might be multithreaded.
> >
> > Add a new status line ("Umask") in /proc/<PID>/status. It contains
> > the file mode creation mask (umask) in octal. It is only shown for
> > tasks which have task->fs.
> >
> > This patch is adapted from one originally written by Pierre Carrier.
> >
> >
> > The use case is that we have endless trouble with people setting weird
> > umask() values (usually on the grounds of "security"), and then everything
> > breaking. I'm on the hook to fix these. We'd like to add debugging to
> > our program so we can dump out the umask in debug reports.
> >
> > Previous versions of the patch used a syscall so you could only read your
> > own umask. That's all I need. However there was quite a lot of push-back
> > from those, so this new version exports it in /proc.
> >
> > See:
> >
>
> lkmlo.org links tend to be rather unstable from my experience. Please
> try to use lkml.kernel.org/[rg]/$msg_id as much as possible
>
> > https://lkml.org/lkml/2016/4/13/704 [umask2]
>
> http://lkml.kernel.org/r/1460574336-18930-1-git-send-email-rjones@redhat.com
>
> > https://lkml.org/lkml/2016/4/13/487 [getumask]
>
> http://lkml.kernel.org/r/1460547786-16766-1-git-send-email-rjones@redhat.com
FWIW this was heavily edited from my original commit message. My
original commit message (minus the Signed-off-by etc) was:
procfs: expose umask in /proc/<PID>/status
It's not possible to read the process umask without also modifying it,
which is what umask(2) does. A library cannot read umask safely,
especially if the main program might be multithreaded.
Add a new status line ("Umask") in /proc/<PID>/status. It contains
the file mode creation mask (umask) in octal. It is only shown for
tasks which have task->fs.
This patch is adapted from one originally written by Pierre Carrier.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
--
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:[~2016-04-25 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <571a8f8c.6RbLc3Gh9b0xGfe6%akpm@linux-foundation.org>
2016-04-25 9:31 ` Michal Hocko
2016-04-25 12:12 ` Richard W.M. Jones [this message]
2016-04-25 12:19 ` Michal Hocko
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=20160425121219.GQ11600@redhat.com \
--to=rjones@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jmarchan@redhat.com \
--cc=keescook@chromium.org \
--cc=koct9i@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=pierre@spotify.com \
--cc=tytso@mit.edu \
/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