Hi Rik,
Thanks for the blazingly fast response :-)
On 9 October 2017 at 21:08, Rik van Riel wrote:
> On Mon, 2017-10-09 at 21:06 +0200, Michael Kerrisk (man-pages) wrote:
>> Hi Rik,
>>
>> I have a follow-up question re wipe-on-fork. What are the semantics
>> for this setting
Hi Rik,
Thanks for the blazingly fast response :-)
On 9 October 2017 at 21:08, Rik van Riel wrote:
> On Mon, 2017-10-09 at 21:06 +0200, Michael Kerrisk (man-pages) wrote:
>> Hi Rik,
>>
>> I have a follow-up question re wipe-on-fork. What are the semantics
>> for this setting with respect to
On Mon, 2017-10-09 at 21:06 +0200, Michael Kerrisk (man-pages) wrote:
> Hi Rik,
>
> I have a follow-up question re wipe-on-fork. What are the semantics
> for this setting with respect to fork() and exec()? That is, in the
> child of a fork(), does the flag remain set for the specified address
>
On Mon, 2017-10-09 at 21:06 +0200, Michael Kerrisk (man-pages) wrote:
> Hi Rik,
>
> I have a follow-up question re wipe-on-fork. What are the semantics
> for this setting with respect to fork() and exec()? That is, in the
> child of a fork(), does the flag remain set for the specified address
>
Hi Rik,
I have a follow-up question re wipe-on-fork. What are the semantics
for this setting with respect to fork() and exec()? That is, in the
child of a fork(), does the flag remain set for the specified address
range? (My quick read of the source suggests yes, but I have not
tested.) And, when
Hi Rik,
I have a follow-up question re wipe-on-fork. What are the semantics
for this setting with respect to fork() and exec()? That is, in the
child of a fork(), does the flag remain set for the specified address
range? (My quick read of the source suggests yes, but I have not
tested.) And, when
On Tue, 2017-09-19 at 21:07 +0200, Michael Kerrisk (man-pages) wrote:
> Thanks. I applied this, and tweaked the madvise.2 text a little, to
> read as follows (please let me know if I messed anything up):
>
> MADV_WIPEONFORK (since Linux 4.14)
> Present the child process with
On Tue, 2017-09-19 at 21:07 +0200, Michael Kerrisk (man-pages) wrote:
> Thanks. I applied this, and tweaked the madvise.2 text a little, to
> read as follows (please let me know if I messed anything up):
>
> MADV_WIPEONFORK (since Linux 4.14)
> Present the child process with
Hello Rik, (and Colm)
On 09/14/2017 09:05 PM, Rik van Riel wrote:
> v2: implement the improvements suggested by Colm, and add
> Colm's text to the fork.2 man page
> (Colm, I have added a signed-off-by in your name - is that ok?)
>
> Add MADV_WIPEONFORK and MADV_KEEPONFORK documentation
Hello Rik, (and Colm)
On 09/14/2017 09:05 PM, Rik van Riel wrote:
> v2: implement the improvements suggested by Colm, and add
> Colm's text to the fork.2 man page
> (Colm, I have added a signed-off-by in your name - is that ok?)
>
> Add MADV_WIPEONFORK and MADV_KEEPONFORK documentation
On Thu, Sep 14, 2017 at 12:05 PM, Rik van Riel wrote:
> v2: implement the improvements suggested by Colm, and add
> Colm's text to the fork.2 man page
> (Colm, I have added a signed-off-by in your name - is that ok?)
Yep, that's ok! Whole thing LGTM.
--
Colm
On Thu, Sep 14, 2017 at 12:05 PM, Rik van Riel wrote:
> v2: implement the improvements suggested by Colm, and add
> Colm's text to the fork.2 man page
> (Colm, I have added a signed-off-by in your name - is that ok?)
Yep, that's ok! Whole thing LGTM.
--
Colm
v2: implement the improvements suggested by Colm, and add
Colm's text to the fork.2 man page
(Colm, I have added a signed-off-by in your name - is that ok?)
Add MADV_WIPEONFORK and MADV_KEEPONFORK documentation to
madvise.2. The new functionality was recently merged by
Linus, and should
v2: implement the improvements suggested by Colm, and add
Colm's text to the fork.2 man page
(Colm, I have added a signed-off-by in your name - is that ok?)
Add MADV_WIPEONFORK and MADV_KEEPONFORK documentation to
madvise.2. The new functionality was recently merged by
Linus, and should
14 matches
Mail list logo