On 07/26/2016 04:54 AM, Andrew Vagin wrote:
On Mon, Jul 25, 2016 at 09:59:43AM -0500, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" <mtk.manpa...@gmail.com> writes:
[snip]
[snip]
So, from my point of view, the important piece that was missing from
your commit mess
On 07/26/2016 04:54 AM, Andrew Vagin wrote:
On Mon, Jul 25, 2016 at 09:59:43AM -0500, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" writes:
[snip]
[snip]
So, from my point of view, the important piece that was missing from
your commit message was the note to use readl
Hi Eric,
On 07/25/2016 03:18 PM, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" <mtk.manpa...@gmail.com> writes:
Hi Andrey,
On 07/22/2016 08:25 PM, Andrey Vagin wrote:
On Thu, Jul 21, 2016 at 11:48 PM, Michael Kerrisk (man-pages)
<mtk.manpa...@gmail.com> wrot
Hi Eric,
On 07/25/2016 03:18 PM, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" writes:
Hi Andrey,
On 07/22/2016 08:25 PM, Andrey Vagin wrote:
On Thu, Jul 21, 2016 at 11:48 PM, Michael Kerrisk (man-pages)
wrote:
Hi Andrey,
On 07/21/2016 11:06 PM, Andrew Vagin wrote
Hi Andrey,
On 07/22/2016 08:25 PM, Andrey Vagin wrote:
On Thu, Jul 21, 2016 at 11:48 PM, Michael Kerrisk (man-pages)
<mtk.manpa...@gmail.com> wrote:
Hi Andrey,
On 07/21/2016 11:06 PM, Andrew Vagin wrote:
On Thu, Jul 21, 2016 at 04:41:12PM +0200, Michael Kerrisk (man-pages)
wrote
Hi Andrey,
On 07/22/2016 08:25 PM, Andrey Vagin wrote:
On Thu, Jul 21, 2016 at 11:48 PM, Michael Kerrisk (man-pages)
wrote:
Hi Andrey,
On 07/21/2016 11:06 PM, Andrew Vagin wrote:
On Thu, Jul 21, 2016 at 04:41:12PM +0200, Michael Kerrisk (man-pages)
wrote:
Hi Andrey,
On 07/14/2016 08:20
;Eric W. Biederman" <ebied...@xmission.com>
Cc: James Bottomley <james.bottom...@hansenpartnership.com>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpa...@gmail.com>
Cc: "W. Trevor King" <wk...@tremily.us>
Cc: Alexander Viro <v...@zeniv.linux.org.uk
;Eric W. Biederman"
Cc: James Bottomley
Cc: "Michael Kerrisk (man-pages)"
Cc: "W. Trevor King"
Cc: Alexander Viro
Cc: Serge Hallyn
--
2.5.5
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
Released: 2016-07-17, Ulm
New and rewritten pages
---
ioctl_fideduperange.2
Darrick J. Wong [Christoph Hellwig, Michael Kerrisk]
New page documenting the FIDEDUPERANGE ioctl
Document the FIDEDUPERANGE ioctl, formerly known
Released: 2016-07-17, Ulm
New and rewritten pages
---
ioctl_fideduperange.2
Darrick J. Wong [Christoph Hellwig, Michael Kerrisk]
New page documenting the FIDEDUPERANGE ioctl
Document the FIDEDUPERANGE ioctl, formerly known
Hello Konstantin,
On 13 July 2016 at 20:37, Konstantin Ryabitsev <mri...@kernel.org> wrote:
> On Wed, Jul 13, 2016 at 08:28:18PM +0200, Michael Kerrisk (man-pages) wrote:
>> Hello Konstantin,
>>
>> The man-pages Bugzilla component (as well as other components on
>&g
Hello Konstantin,
On 13 July 2016 at 20:37, Konstantin Ryabitsev wrote:
> On Wed, Jul 13, 2016 at 08:28:18PM +0200, Michael Kerrisk (man-pages) wrote:
>> Hello Konstantin,
>>
>> The man-pages Bugzilla component (as well as other components on
>> Bugzilla by the look o
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
On 07/08/2016 05:26 AM, James Bottomley wrote:
On Thu, 2016-07-07 at 20:00 -0700, Andrew Vagin wrote:
On Thu, Jul 07, 2016 at 07:16:18PM -0700, Andrew Vagin wrote:
On Thu, Jul 07, 2016 at 12:17:35PM -0700, James Bottomley wrote:
On Thu, 2016-07-07 at 20:21 +0200, Michael Kerrisk (man-pages
On 07/08/2016 05:26 AM, James Bottomley wrote:
On Thu, 2016-07-07 at 20:00 -0700, Andrew Vagin wrote:
On Thu, Jul 07, 2016 at 07:16:18PM -0700, Andrew Vagin wrote:
On Thu, Jul 07, 2016 at 12:17:35PM -0700, James Bottomley wrote:
On Thu, 2016-07-07 at 20:21 +0200, Michael Kerrisk (man-pages
On 07/07/2016 09:17 PM, James Bottomley wrote:
On Thu, 2016-07-07 at 20:21 +0200, Michael Kerrisk (man-pages) wrote:
On 7 July 2016 at 17:01, James Bottomley
<james.bottom...@hansenpartnership.com> wrote:
[Serge already answered the parenting issue]
On Thu, 2016-07-07 at 08:36 -0500, S
On 07/07/2016 09:17 PM, James Bottomley wrote:
On Thu, 2016-07-07 at 20:21 +0200, Michael Kerrisk (man-pages) wrote:
On 7 July 2016 at 17:01, James Bottomley
wrote:
[Serge already answered the parenting issue]
On Thu, 2016-07-07 at 08:36 -0500, Serge E. Hallyn wrote:
Hm. Probably best
On 7 July 2016 at 17:01, James Bottomley
<james.bottom...@hansenpartnership.com> wrote:
> On Thu, 2016-07-07 at 08:36 -0500, Serge E. Hallyn wrote:
>> Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com):
>> > Hi Serge,
>> >
>> > On 6 July 2016 a
On 7 July 2016 at 17:01, James Bottomley
wrote:
> On Thu, 2016-07-07 at 08:36 -0500, Serge E. Hallyn wrote:
>> Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com):
>> > Hi Serge,
>> >
>> > On 6 July 2016 at 16:13, Serge E. Hallyn wrote:
>> &g
Hi Serge,
On 6 July 2016 at 16:13, Serge E. Hallyn <se...@hallyn.com> wrote:
> On Wed, Jul 06, 2016 at 10:41:48AM +0200, Michael Kerrisk (man-pages) wrote:
>> [Rats! Doing now what I should have down to start with. Looping some
>> lists and CRIU and other pos
Hi Serge,
On 6 July 2016 at 16:13, Serge E. Hallyn wrote:
> On Wed, Jul 06, 2016 at 10:41:48AM +0200, Michael Kerrisk (man-pages) wrote:
>> [Rats! Doing now what I should have down to start with. Looping some
>> lists and CRIU and other possibly relevant people into this
[Rats! Doing now what I should have down to start with. Looping some
lists and CRIU and other possibly relevant people into this
conversation]
Hi Eric,
On 5 July 2016 at 23:47, Eric W. Biederman <ebied...@xmission.com> wrote:
> "Michael Kerrisk (man-pages)" <mtk.manp
[Rats! Doing now what I should have down to start with. Looping some
lists and CRIU and other possibly relevant people into this
conversation]
Hi Eric,
On 5 July 2016 at 23:47, Eric W. Biederman wrote:
> "Michael Kerrisk (man-pages)" writes:
>
>> Hi Eric,
>>
>&g
Hi Kees,
On 06/28/2016 10:55 PM, Kees Cook wrote:
On Mon, Jun 27, 2016 at 11:11 PM, Michael Kerrisk (man-pages)
<mtk.manpa...@gmail.com> wrote:
Hi Jann,
On 06/25/2016 04:30 PM, Jann Horn wrote:
On Sat, Jun 25, 2016 at 09:30:43AM +0200, Michael Kerrisk (man-pages)
wrote:
Hi Kee
Hi Kees,
On 06/28/2016 10:55 PM, Kees Cook wrote:
On Mon, Jun 27, 2016 at 11:11 PM, Michael Kerrisk (man-pages)
wrote:
Hi Jann,
On 06/25/2016 04:30 PM, Jann Horn wrote:
On Sat, Jun 25, 2016 at 09:30:43AM +0200, Michael Kerrisk (man-pages)
wrote:
Hi Kees,
So, last year, I added some
arget process.
Nit: The grammar in this sentence seems wrong to me.
s/or it have/or it must have/?
Yep, thanks for catching that. Fixed now.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
arget process.
Nit: The grammar in this sentence seems wrong to me.
s/or it have/or it must have/?
Yep, thanks for catching that. Fixed now.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
Hi Jann,
On 06/25/2016 04:30 PM, Jann Horn wrote:
On Sat, Jun 25, 2016 at 09:30:43AM +0200, Michael Kerrisk (man-pages) wrote:
Hi Kees,
So, last year, I added some documentation to ptrace(2) to describe
the Yama ptrace_scope file. I don't think I asked you for review
at the time
Hi Jann,
On 06/25/2016 04:30 PM, Jann Horn wrote:
On Sat, Jun 25, 2016 at 09:30:43AM +0200, Michael Kerrisk (man-pages) wrote:
Hi Kees,
So, last year, I added some documentation to ptrace(2) to describe
the Yama ptrace_scope file. I don't think I asked you for review
at the time
Hi Jann,
Patches such as this really should CC linux-api@ (added).
On Sat, Jun 25, 2016 at 2:23 AM, Jann Horn wrote:
> This allows the admin of a user namespace to mark the namespace as
> transparent. All other namespaces, by default, are opaque.
>
> While the current behavior
Hi Jann,
Patches such as this really should CC linux-api@ (added).
On Sat, Jun 25, 2016 at 2:23 AM, Jann Horn wrote:
> This allows the admin of a user namespace to mark the namespace as
> transparent. All other namespaces, by default, are opaque.
>
> While the current behavior of user
process may perform PTRACE_MODE_ATTACH operations or
trace children that employ PTRACE_TRACEME.
Once this value has been written to the file, it cannot
be changed.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc
process may perform PTRACE_MODE_ATTACH operations or
trace children that employ PTRACE_TRACEME.
Once this value has been written to the file, it cannot
be changed.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc
On 06/24/2016 05:18 PM, Casey Schaufler wrote:
On 6/24/2016 1:40 AM, Michael Kerrisk (man-pages) wrote:
On 06/22/2016 11:11 PM, Kees Cook wrote:
On Wed, Jun 22, 2016 at 12:21 PM, Michael Kerrisk (man-pages)
<mtk.manpa...@gmail.com> wrote:
On 06/21/2016 10:55 PM, Jann Horn wrote:
On 06/24/2016 05:18 PM, Casey Schaufler wrote:
On 6/24/2016 1:40 AM, Michael Kerrisk (man-pages) wrote:
On 06/22/2016 11:11 PM, Kees Cook wrote:
On Wed, Jun 22, 2016 at 12:21 PM, Michael Kerrisk (man-pages)
wrote:
On 06/21/2016 10:55 PM, Jann Horn wrote:
On Tue, Jun 21, 2016 at 11:41:16AM
On 06/24/2016 11:52 AM, Thomas Gleixner wrote:
On Fri, 24 Jun 2016, Michael Kerrisk (man-pages) wrote:
By the way, I just realized something that wasn't initially obvious
to me, and documented it in the futex(2) man page:
Note: for FUTEX_WAIT, timeout is interpreted
On 06/24/2016 11:52 AM, Thomas Gleixner wrote:
On Fri, 24 Jun 2016, Michael Kerrisk (man-pages) wrote:
By the way, I just realized something that wasn't initially obvious
to me, and documented it in the futex(2) man page:
Note: for FUTEX_WAIT, timeout is interpreted
Hi Eric,
On 06/23/2016 09:04 PM, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" <mtk.manpa...@gmail.com> writes:
Hi Eric,
On 06/21/2016 09:55 PM, Eric W. Biederman wrote:
Hmm.
When I gave this level of detail about the user namespace permission
checks you ga
Hi Eric,
On 06/23/2016 09:04 PM, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" writes:
Hi Eric,
On 06/21/2016 09:55 PM, Eric W. Biederman wrote:
Hmm.
When I gave this level of detail about the user namespace permission
checks you gave me some flac
On 06/22/2016 11:11 PM, Kees Cook wrote:
On Wed, Jun 22, 2016 at 12:21 PM, Michael Kerrisk (man-pages)
<mtk.manpa...@gmail.com> wrote:
On 06/21/2016 10:55 PM, Jann Horn wrote:
On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages)
wrote:
5. The kern
On 06/22/2016 11:11 PM, Kees Cook wrote:
On Wed, Jun 22, 2016 at 12:21 PM, Michael Kerrisk (man-pages)
wrote:
On 06/21/2016 10:55 PM, Jann Horn wrote:
On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages)
wrote:
5. The kernel LSM security_ptrace_access_check
Stephen,
On 06/23/2016 08:05 PM, Stephen Smalley wrote:
On 06/21/2016 05:41 AM, Michael Kerrisk (man-pages) wrote:
Hi Jann, Stephen, et al.
Jann, since you recently committed a patch in this area, and Stephen,
since you committed 006ebb40d3d much further back in time, I wonder if
you might
Stephen,
On 06/23/2016 08:05 PM, Stephen Smalley wrote:
On 06/21/2016 05:41 AM, Michael Kerrisk (man-pages) wrote:
Hi Jann, Stephen, et al.
Jann, since you recently committed a patch in this area, and Stephen,
since you committed 006ebb40d3d much further back in time, I wonder if
you might
On 06/23/2016 08:56 PM, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" <mtk.manpa...@gmail.com> writes:
Hi Oleg,
On 06/22/2016 11:51 PM, Oleg Nesterov wrote:
On 06/21, Eric W. Biederman wrote:
Adding Oleg just because he seems to do most of the ptrace related
mainte
On 06/23/2016 08:56 PM, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" writes:
Hi Oleg,
On 06/22/2016 11:51 PM, Oleg Nesterov wrote:
On 06/21, Eric W. Biederman wrote:
Adding Oleg just because he seems to do most of the ptrace related
maintenance these days.
so I hav
On 06/23/2016 09:53 PM, Darren Hart wrote:
On Thu, Jun 23, 2016 at 08:35:15PM +0200, Michael Kerrisk (man-pages) wrote:
Hi Darren,
On 06/23/2016 06:16 PM, Darren Hart wrote:
On Thu, Jun 23, 2016 at 03:40:36PM +0200, Thomas Gleixner wrote:
On Thu, 23 Jun 2016, Michael Kerrisk (man-pages
On 06/23/2016 09:53 PM, Darren Hart wrote:
On Thu, Jun 23, 2016 at 08:35:15PM +0200, Michael Kerrisk (man-pages) wrote:
Hi Darren,
On 06/23/2016 06:16 PM, Darren Hart wrote:
On Thu, Jun 23, 2016 at 03:40:36PM +0200, Thomas Gleixner wrote:
On Thu, 23 Jun 2016, Michael Kerrisk (man-pages
code.
And as a follow-on, what is the reason for FUTEX_LOCK_PI only using
CLOCK_REALTIME? It seems reasonable to me that a user may want to wait a
specific amount of time, regardless of wall time.
Yes, that's another weird inconsistency.
Thanks,
Michael
--
Michael Kerrisk
Linux man-p
code.
And as a follow-on, what is the reason for FUTEX_LOCK_PI only using
CLOCK_REALTIME? It seems reasonable to me that a user may want to wait a
specific amount of time, regardless of wall time.
Yes, that's another weird inconsistency.
Thanks,
Michael
--
Michael Kerrisk
Linux man-p
Hi Darren,
On 06/23/2016 06:16 PM, Darren Hart wrote:
On Thu, Jun 23, 2016 at 03:40:36PM +0200, Thomas Gleixner wrote:
On Thu, 23 Jun 2016, Michael Kerrisk (man-pages) wrote:
On 06/23/2016 09:18 AM, Thomas Gleixner wrote:
Once upon a time, you told me the following:
On 15 May 2014 at 16:14
Hi Darren,
On 06/23/2016 06:16 PM, Darren Hart wrote:
On Thu, Jun 23, 2016 at 03:40:36PM +0200, Thomas Gleixner wrote:
On Thu, 23 Jun 2016, Michael Kerrisk (man-pages) wrote:
On 06/23/2016 09:18 AM, Thomas Gleixner wrote:
Once upon a time, you told me the following:
On 15 May 2014 at 16:14
time in
CLOCK_REALTIME independent of the CLOCK_REALTIME flag.
Once upon a time, you told me the following:
On 15 May 2014 at 16:14, Thomas Gleixner <t...@linutronix.de> wrote:
On Thu, 15 May 2014, Michael Kerrisk (man-pages) wrote:
And that universe would love to have your doc
+ if (cmd == FUTEX_WAIT && !(op & FUTEX_CLOCK_REALTIME))
t = ktime_add_safe(ktime_get(), t);
tp =
}
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
time in
CLOCK_REALTIME independent of the CLOCK_REALTIME flag.
Once upon a time, you told me the following:
On 15 May 2014 at 16:14, Thomas Gleixner wrote:
On Thu, 15 May 2014, Michael Kerrisk (man-pages) wrote:
And that universe would love to have your documentation of
FUTEX_WAKE_BI
+ if (cmd == FUTEX_WAIT && !(op & FUTEX_CLOCK_REALTIME))
t = ktime_add_safe(ktime_get(), t);
tp =
}
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
Hi Jann,
Thanks for your further review. Follow-up of one point below.
On 06/23/2016 12:44 AM, Jann Horn wrote:
On Wed, Jun 22, 2016 at 09:21:29PM +0200, Michael Kerrisk (man-pages) wrote:
On 06/21/2016 10:55 PM, Jann Horn wrote:
On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man
Hi Jann,
Thanks for your further review. Follow-up of one point below.
On 06/23/2016 12:44 AM, Jann Horn wrote:
On Wed, Jun 22, 2016 at 09:21:29PM +0200, Michael Kerrisk (man-pages) wrote:
On 06/21/2016 10:55 PM, Jann Horn wrote:
On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man
ginning
to think they can depend upon bugs in the implementation": when it
comes to breaking the ABI, the presence or absence of documentation
doesn't save us on that point (Linus has a few times made his position
wrt to documentation clear).
Cheers,
Michael
--
Michael Kerrisk
Li
ginning
to think they can depend upon bugs in the implementation": when it
comes to breaking the ABI, the presence or absence of documentation
doesn't save us on that point (Linus has a few times made his position
wrt to documentation clear).
Cheers,
Michael
--
Michael Kerrisk
Li
On 06/22/2016 11:11 PM, Kees Cook wrote:
On Wed, Jun 22, 2016 at 12:21 PM, Michael Kerrisk (man-pages)
<mtk.manpa...@gmail.com> wrote:
On 06/21/2016 10:55 PM, Jann Horn wrote:
On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages)
wrote:
5. The kern
On 06/22/2016 11:11 PM, Kees Cook wrote:
On Wed, Jun 22, 2016 at 12:21 PM, Michael Kerrisk (man-pages)
wrote:
On 06/21/2016 10:55 PM, Jann Horn wrote:
On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages)
wrote:
5. The kernel LSM security_ptrace_access_check
Hi Jann,
On 06/21/2016 10:55 PM, Jann Horn wrote:
On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages) wrote:
Hi Jann, Stephen, et al.
Jann, since you recently committed a patch in this area, and Stephen,
since you committed 006ebb40d3d much further back in time, I wonder
Hi Jann,
On 06/21/2016 10:55 PM, Jann Horn wrote:
On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages) wrote:
Hi Jann, Stephen, et al.
Jann, since you recently committed a patch in this area, and Stephen,
since you committed 006ebb40d3d much further back in time, I wonder
Hi Kees,
On 06/21/2016 10:29 PM, Kees Cook wrote:
On Tue, Jun 21, 2016 at 12:55 PM, Eric W. Biederman
<ebied...@xmission.com> wrote:
Adding Oleg just because he seems to do most of the ptrace related
maintenance these days.
"Michael Kerrisk (man-pages)" <mtk.manpa...@gmai
Hi Kees,
On 06/21/2016 10:29 PM, Kees Cook wrote:
On Tue, Jun 21, 2016 at 12:55 PM, Eric W. Biederman
wrote:
Adding Oleg just because he seems to do most of the ptrace related
maintenance these days.
"Michael Kerrisk (man-pages)" writes:
Hi Jann, Stephen, et al.
Jann, since yo
Hi Eric,
On 06/21/2016 09:55 PM, Eric W. Biederman wrote:
Adding Oleg just because he seems to do most of the ptrace related
maintenance these days.
"Michael Kerrisk (man-pages)" <mtk.manpa...@gmail.com> writes:
Hi Jann, Stephen, et al.
Jann, since you recently c
Hi Eric,
On 06/21/2016 09:55 PM, Eric W. Biederman wrote:
Adding Oleg just because he seems to do most of the ptrace related
maintenance these days.
"Michael Kerrisk (man-pages)" writes:
Hi Jann, Stephen, et al.
Jann, since you recently committed a patch in this area, and Step
e
PTRACE_MODE_READ_FSCREDS check; see ptrace(2).
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
e
PTRACE_MODE_READ_FSCREDS check; see ptrace(2).
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
ichael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
ichael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
On 06/03/2016 12:28 PM, Dave Hansen wrote:
> On 06/02/2016 05:26 PM, Michael Kerrisk (man-pages) wrote:
>> On 06/01/2016 07:17 PM, Dave Hansen wrote:
>>> On 06/01/2016 05:11 PM, Michael Kerrisk (man-pages) wrote:
>>>>>>>>
>>>>>>
On 06/03/2016 12:28 PM, Dave Hansen wrote:
> On 06/02/2016 05:26 PM, Michael Kerrisk (man-pages) wrote:
>> On 06/01/2016 07:17 PM, Dave Hansen wrote:
>>> On 06/01/2016 05:11 PM, Michael Kerrisk (man-pages) wrote:
>>>>>>>>
>>>>>>
On 06/01/2016 07:17 PM, Dave Hansen wrote:
> On 06/01/2016 05:11 PM, Michael Kerrisk (man-pages) wrote:
>>>>>>
>>>>>> If I read this right, it doesn't actually remove any pkey restrictions
>>>>>> that may have been applied while the k
On 06/01/2016 07:17 PM, Dave Hansen wrote:
> On 06/01/2016 05:11 PM, Michael Kerrisk (man-pages) wrote:
>>>>>>
>>>>>> If I read this right, it doesn't actually remove any pkey restrictions
>>>>>> that may have been applied while the k
er that mm have that vma_pkey() set. But, that
> search would be potentially expensive (a walk over all VMAs), or would
> force us to keep a data structure with a count of all the VMAs with a
> given key.
>
> I should probably discuss this behavior in the manpages and address it
s
vma_pkey() set. But, that
> search would be potentially expensive (a walk over all VMAs), or would
> force us to keep a data structure with a count of all the VMAs with a
> given key.
>
> I should probably discuss this behavior in the manpages and address it
s/probably//
And, did I
/mnt/tmp/etc
> # cat /proc/self/mountinfo | grep /tmp/etc
> 164 40 253:1 /etc /tmp/etc rw,relatime shared:100 master:97 - ...
> # chroot /mnt
> # cat /proc/self/mountinfo
> 129 62 253:1 / / rw,relatime shared:97 - ...
> 168 129 253:1 /etc /tmp/etc rw,relatime master:100 propag
/mnt/tmp/etc
> # cat /proc/self/mountinfo | grep /tmp/etc
> 164 40 253:1 /etc /tmp/etc rw,relatime shared:100 master:97 - ...
> # chroot /mnt
> # cat /proc/self/mountinfo
> 129 62 253:1 / / rw,relatime shared:97 - ...
> 168 129 253:1 /etc /tmp/etc rw,relatime master:100 propag
Hello Ram,
On 05/20/2016 06:15 PM, Ram Pai wrote:
> On Fri, May 20, 2016 at 04:24:18PM -0500, Michael Kerrisk (man-pages) wrote:
>> Hello Miklos,
>>
>> I'm working on some better documentation of mount namespaces,
>> and there's a detail that puzzles me, and I hope yo
Hello Ram,
On 05/20/2016 06:15 PM, Ram Pai wrote:
> On Fri, May 20, 2016 at 04:24:18PM -0500, Michael Kerrisk (man-pages) wrote:
>> Hello Miklos,
>>
>> I'm working on some better documentation of mount namespaces,
>> and there's a detail that puzzles me, and I hope yo
seq_printf(m, " propagate_from:%i", dom);
}
]]
But I can't relate that to some user-space semantics. I suppose another
way of asking my question is: how could I create a slave that is
propagating from a peer group other than it's immediate master?
Cheers,
Michael
--
M
seq_printf(m, " propagate_from:%i", dom);
}
]]
But I can't relate that to some user-space semantics. I suppose another
way of asking my question is: how could I create a slave that is
propagating from a peer group other than it's immediate master?
Cheers,
Michael
--
M
New and rewritten pages
---
cgroups.7
Serge Hallyn, Michael Kerrisk
New page documenting cgroups
cgroup_namespaces.7
Michael Kerrisk [Serge Hallyn]
New page describing cgroup namespaces
Newly documented interfaces in existing pages
New and rewritten pages
---
cgroups.7
Serge Hallyn, Michael Kerrisk
New page documenting cgroups
cgroup_namespaces.7
Michael Kerrisk [Serge Hallyn]
New page describing cgroup namespaces
Newly documented interfaces in existing pages
Hi Serge,
On 6 May 2016 at 19:33, Serge E. Hallyn <se...@hallyn.com> wrote:
> Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com):
>> Hi Serge,
>>
>> I'll add my own notes below, as much as anything in order to convince
>> myself that I understand what's
Hi Serge,
On 6 May 2016 at 19:33, Serge E. Hallyn wrote:
> Quoting Michael Kerrisk (man-pages) (mtk.manpa...@gmail.com):
>> Hi Serge,
>>
>> I'll add my own notes below, as much as anything in order to convince
>> myself that I understand what's going on.
>>
&
f the shell run by unshare is
in the cgroup.procs file of this cgroup):
# ls /mnt/freezer/
cgroup.clone_children freezer.parent_freezing freezer.state tasks
cgroup.procs freezer.self_freezing notify_on_release
# echo $$
3164
# cat /mnt/freezer/cgroup.procs
2653
f the shell run by unshare is
in the cgroup.procs file of this cgroup):
# ls /mnt/freezer/
cgroup.clone_children freezer.parent_freezing freezer.state tasks
cgroup.procs freezer.self_freezing notify_on_release
# echo $$
3164
# cat /mnt/freezer/cgroup.procs
2653
he
> file, then the kernel silently writes security.nscapability instead.
>
> The biggest drawback of (1) would be any tar-like program trying
> to restore a file which had security.capability, needing to know
> to detect its userns and write the security.nscapability instead.
> The draw
e biggest drawback of (1) would be any tar-like program trying
> to restore a file which had security.capability, needing to know
> to detect its userns and write the security.nscapability instead.
> The drawback of (2) is ~\o/~ magic.
I have only (minor) thoughts from the interface pers
Works can't express the importance of adding this system call!
Thanks so much for proposing and implementing it!
Acked-by: Michael Kerrisk <mtk.manpa...@gmail.com>
Cheers,
Michael
> Signed-off-by: David Gstir <da...@sigma-star.at>
> Signed-off-by: Richard Weinberger <rich..
the importance of adding this system call!
Thanks so much for proposing and implementing it!
Acked-by: Michael Kerrisk
Cheers,
Michael
> Signed-off-by: David Gstir
> Signed-off-by: Richard Weinberger
> ---
> arch/x86/entry/syscalls/syscall_64.tbl | 1 +
> include/linux/syscalls.h
New and rewritten pages
---
copy_file_range.2
Anna Schumaker [Darrick J. Wong, Christoph Hellwig, Michael Kerrisk]
New page documenting copy_file_range()
personality.2
Michael Kerrisk
This page has been greatly expanded, to add descriptions
New and rewritten pages
---
copy_file_range.2
Anna Schumaker [Darrick J. Wong, Christoph Hellwig, Michael Kerrisk]
New page documenting copy_file_range()
personality.2
Michael Kerrisk
This page has been greatly expanded, to add descriptions
Hi Jason,
On 03/15/2016 11:35 AM, Jason Baron wrote:
> Hi Michael,
>
> On 03/14/2016 05:03 PM, Michael Kerrisk (man-pages) wrote:
>> Hi Jason,
>>
>> On 03/15/2016 09:01 AM, Michael Kerrisk (man-pages) wrote:
>>> Hi Jason,
>>>
>>> On 03/15/201
Hi Jason,
On 03/15/2016 11:35 AM, Jason Baron wrote:
> Hi Michael,
>
> On 03/14/2016 05:03 PM, Michael Kerrisk (man-pages) wrote:
>> Hi Jason,
>>
>> On 03/15/2016 09:01 AM, Michael Kerrisk (man-pages) wrote:
>>> Hi Jason,
>>>
>>> On 03/15/201
Hi Jason,
On 03/15/2016 09:01 AM, Michael Kerrisk (man-pages) wrote:
> Hi Jason,
>
> On 03/15/2016 08:32 AM, Jason Baron wrote:
>>
>>
>> On 03/14/2016 01:47 PM, Michael Kerrisk (man-pages) wrote:
>>> [Restoring CC, which I see I accidentally dropped, one it
Hi Jason,
On 03/15/2016 09:01 AM, Michael Kerrisk (man-pages) wrote:
> Hi Jason,
>
> On 03/15/2016 08:32 AM, Jason Baron wrote:
>>
>>
>> On 03/14/2016 01:47 PM, Michael Kerrisk (man-pages) wrote:
>>> [Restoring CC, which I see I accidentally dropped, one it
901 - 1000 of 2778 matches
Mail list logo