On 03/03, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> >> @@ -699,8 +701,6 @@ static void exit_notify(struct task_struct *tsk, int
> >> group_dead)
> >>}
> >>
> >>tsk->exit_state = autoreap ? EXIT_DEAD : EXIT_ZOMBIE;
> >> - if (tsk->exit_state == EXIT_DEAD)
>
On 03/03, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> >> @@ -699,8 +701,6 @@ static void exit_notify(struct task_struct *tsk, int
> >> group_dead)
> >>}
> >>
> >>tsk->exit_state = autoreap ? EXIT_DEAD : EXIT_ZOMBIE;
> >> - if (tsk->exit_state == EXIT_DEAD)
> >> -
ebied...@xmission.com (Eric W. Biederman) writes:
> The big lesson for me, and what was not obvious from your change
> description is that we are changing the user space visible semantics
> of exec+ptrace and that cred_guard_mutex is not at all the problem (as
> we always take cred_guard_mutex in
ebied...@xmission.com (Eric W. Biederman) writes:
> The big lesson for me, and what was not obvious from your change
> description is that we are changing the user space visible semantics
> of exec+ptrace and that cred_guard_mutex is not at all the problem (as
> we always take cred_guard_mutex in
ebied...@xmission.com (Eric W. Biederman) writes:
> ebied...@xmission.com (Eric W. Biederman) writes:
>
>> The big lesson for me, and what was not obvious from your change
>> description is that we are changing the user space visible semantics
>> of exec+ptrace and that cred_guard_mutex is not at
ebied...@xmission.com (Eric W. Biederman) writes:
> ebied...@xmission.com (Eric W. Biederman) writes:
>
>> The big lesson for me, and what was not obvious from your change
>> description is that we are changing the user space visible semantics
>> of exec+ptrace and that cred_guard_mutex is not at
Cc'd linux-api as we are talking about a deliberate user visible API
change here.
Oleg Nesterov writes:
> On 03/02, Eric W. Biederman wrote:
>>
>> Oleg Nesterov writes:
>>
>> > our discussion was a bit confusing, and it seems that we did not
>> > fully
Cc'd linux-api as we are talking about a deliberate user visible API
change here.
Oleg Nesterov writes:
> On 03/02, Eric W. Biederman wrote:
>>
>> Oleg Nesterov writes:
>>
>> > our discussion was a bit confusing, and it seems that we did not
>> > fully convince each other. So let me ask what
On 03/02, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > our discussion was a bit confusing, and it seems that we did not
> > fully convince each other. So let me ask what do you finally think
> > about this fix.
> >
> > Let me repeat. Even if I do not agree with some
On 03/02, Eric W. Biederman wrote:
>
> Oleg Nesterov writes:
>
> > our discussion was a bit confusing, and it seems that we did not
> > fully convince each other. So let me ask what do you finally think
> > about this fix.
> >
> > Let me repeat. Even if I do not agree with some of your
Oleg Nesterov writes:
> Eric,
>
> our discussion was a bit confusing, and it seems that we did not
> fully convince each other. So let me ask what do you finally think
> about this fix.
>
> Let me repeat. Even if I do not agree with some of your objections,
> I do agree that 1/2
Oleg Nesterov writes:
> Eric,
>
> our discussion was a bit confusing, and it seems that we did not
> fully convince each other. So let me ask what do you finally think
> about this fix.
>
> Let me repeat. Even if I do not agree with some of your objections,
> I do agree that 1/2 does not look
Eric,
our discussion was a bit confusing, and it seems that we did not
fully convince each other. So let me ask what do you finally think
about this fix.
Let me repeat. Even if I do not agree with some of your objections,
I do agree that 1/2 does not look nice and clean. And we seem to
agree
Eric,
our discussion was a bit confusing, and it seems that we did not
fully convince each other. So let me ask what do you finally think
about this fix.
Let me repeat. Even if I do not agree with some of your objections,
I do agree that 1/2 does not look nice and clean. And we seem to
agree
Hello,
Lets finally fix this problem, it was reported several times. I still think that
in the longer term we should (try to) rework the security hooks and (partially)
revert this change, but this is not trivial and we need something backportable
anyway.
Eric, Jann, we already discussed this
Hello,
Lets finally fix this problem, it was reported several times. I still think that
in the longer term we should (try to) rework the security hooks and (partially)
revert this change, but this is not trivial and we need something backportable
anyway.
Eric, Jann, we already discussed this
16 matches
Mail list logo