On Wed, Nov 01, 2017 at 12:20:52PM -0500, Eric W. Biederman wrote:
> Well the way I was hearing the conversation was that there was a patch
> that fixed a real bug, but it was wrong because checkpatch complained
> about it.
>
> So I don't even know if the warning is a problem. But blocking bug
>
Joe Perches writes:
> On Wed, 2017-11-01 at 06:08 -0500, Eric W. Biederman wrote:
>> I won't listen to checkpatch when it is wrong.
>
> Always a good idea.
>
> btw: what is checkpatch wrong about this time?
Well the way I was hearing the conversation was that there was a patch
that fixed a real
On Wed, 2017-11-01 at 06:08 -0500, Eric W. Biederman wrote:
> I won't listen to checkpatch when it is wrong.
Always a good idea.
btw: what is checkpatch wrong about this time?
On Wed, Nov 01, 2017 at 02:05:39PM +0100, Peter Zijlstra wrote:
> On Wed, Nov 01, 2017 at 06:08:35AM -0500, Eric W. Biederman wrote:
> > Nikolay Borisov writes:
> >
> > > On 1.11.2017 01:48, Eric W. Biederman wrote:
> > >>
> > >> This is important so reading /proc//{uid_map,gid_map,projid_map}
On Wed, Nov 01, 2017 at 03:16:54PM +0100, Peter Zijlstra wrote:
> On Wed, Nov 01, 2017 at 03:01:45PM +0100, Christian Brauner wrote:
> > Tbf, this isn't solely Eric's fault. I'm to blame here too since I didn't
> > document the already existing smb_rmb()s and the new one I introduced when
> > writi
On Wed, Nov 01, 2017 at 03:01:45PM +0100, Christian Brauner wrote:
> Tbf, this isn't solely Eric's fault. I'm to blame here too since I didn't
> document the already existing smb_rmb()s and the new one I introduced when
> writing the patches. I didn't know that there was a hard-set requirement to
>
On Wed, Nov 01, 2017 at 02:05:39PM +0100, Peter Zijlstra wrote:
> On Wed, Nov 01, 2017 at 06:08:35AM -0500, Eric W. Biederman wrote:
> > Nikolay Borisov writes:
> >
> > > On 1.11.2017 01:48, Eric W. Biederman wrote:
> > >>
> > >> This is important so reading /proc//{uid_map,gid_map,projid_map}
On Wed, Nov 01, 2017 at 06:08:35AM -0500, Eric W. Biederman wrote:
> Nikolay Borisov writes:
>
> > On 1.11.2017 01:48, Eric W. Biederman wrote:
> >>
> >> This is important so reading /proc//{uid_map,gid_map,projid_map} while
> >> the map is being written does not do strange things.
> >>
> >> S
[CCing some memory-barriers people + checkpatch maintainers]
On 1.11.2017 13:08, Eric W. Biederman wrote:
> Nikolay Borisov writes:
>
>> On 1.11.2017 01:48, Eric W. Biederman wrote:
>>>
>>> This is important so reading /proc//{uid_map,gid_map,projid_map} while
>>> the map is being written does
Nikolay Borisov writes:
> On 1.11.2017 01:48, Eric W. Biederman wrote:
>>
>> This is important so reading /proc//{uid_map,gid_map,projid_map} while
>> the map is being written does not do strange things.
>>
>> Signed-off-by: "Eric W. Biederman"
>> ---
>> kernel/user_namespace.c | 6 --
>>
On 1.11.2017 01:48, Eric W. Biederman wrote:
>
> This is important so reading /proc//{uid_map,gid_map,projid_map} while
> the map is being written does not do strange things.
>
> Signed-off-by: "Eric W. Biederman"
> ---
> kernel/user_namespace.c | 6 --
> 1 file changed, 4 insertions(+),
This is important so reading /proc//{uid_map,gid_map,projid_map} while
the map is being written does not do strange things.
Signed-off-by: "Eric W. Biederman"
---
kernel/user_namespace.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/user_namespace.c b/kernel/u
12 matches
Mail list logo
