Radoslaw Burny writes:
> On Tue, Nov 27, 2018 at 6:29 AM Eric W. Biederman
> wrote:
>
> Luis Chamberlain writes:
>
> > On Mon, Nov 26, 2018 at 06:26:07PM +0100, Radoslaw Burny wrote:
> >> Due to a recent commit (d151ddc00498 - fs: Update i_[ug]id_(read|write)
> >> to translate relative to
Radoslaw Burny writes:
> On Tue, Nov 27, 2018 at 6:29 AM Eric W. Biederman
> wrote:
>
> Luis Chamberlain writes:
>
> > On Mon, Nov 26, 2018 at 06:26:07PM +0100, Radoslaw Burny wrote:
> >> Due to a recent commit (d151ddc00498 - fs: Update i_[ug]id_(read|write)
> >> to translate relative to
On Fri, Nov 30, 2018 at 08:48:11AM -0600, Eric W. Biederman wrote:
> Luis Chamberlain writes:
>
> > The logic seems sensible then, but are we implicating what a container
> > does with its sysctl values onto the entire system? If so, sure, it
> > seems you want this for networking purposes as
On Fri, Nov 30, 2018 at 08:48:11AM -0600, Eric W. Biederman wrote:
> Luis Chamberlain writes:
>
> > The logic seems sensible then, but are we implicating what a container
> > does with its sysctl values onto the entire system? If so, sure, it
> > seems you want this for networking purposes as
Luis Chamberlain writes:
> On Mon, Nov 26, 2018 at 11:29:40PM -0600, Eric W. Biederman wrote:
>> Luis Chamberlain writes:
>> > Thanks for the description of how to run into the issue described but
>> > is there also a practical use case today where this is happening? I ask
>> > as it would be
Luis Chamberlain writes:
> On Mon, Nov 26, 2018 at 11:29:40PM -0600, Eric W. Biederman wrote:
>> Luis Chamberlain writes:
>> > Thanks for the description of how to run into the issue described but
>> > is there also a practical use case today where this is happening? I ask
>> > as it would be
On Fri, Nov 30, 2018 at 2:09 AM Luis Chamberlain wrote:
>
> On Mon, Nov 26, 2018 at 11:29:40PM -0600, Eric W. Biederman wrote:
> > Luis Chamberlain writes:
> > > Thanks for the description of how to run into the issue described but
> > > is there also a practical use case today where this is
On Fri, Nov 30, 2018 at 2:09 AM Luis Chamberlain wrote:
>
> On Mon, Nov 26, 2018 at 11:29:40PM -0600, Eric W. Biederman wrote:
> > Luis Chamberlain writes:
> > > Thanks for the description of how to run into the issue described but
> > > is there also a practical use case today where this is
On Mon, Nov 26, 2018 at 11:29:40PM -0600, Eric W. Biederman wrote:
> Luis Chamberlain writes:
> > Thanks for the description of how to run into the issue described but
> > is there also a practical use case today where this is happening? I ask
> > as it would be good to know the severity of the
On Mon, Nov 26, 2018 at 11:29:40PM -0600, Eric W. Biederman wrote:
> Luis Chamberlain writes:
> > Thanks for the description of how to run into the issue described but
> > is there also a practical use case today where this is happening? I ask
> > as it would be good to know the severity of the
Luis Chamberlain writes:
> On Mon, Nov 26, 2018 at 06:26:07PM +0100, Radoslaw Burny wrote:
>> Due to a recent commit (d151ddc00498 - fs: Update i_[ug]id_(read|write)
>> to translate relative to s_user_ns),
>
> Recent? This is commit is from 2014 and present upstream since v4.8.
> And the commit
Luis Chamberlain writes:
> On Mon, Nov 26, 2018 at 06:26:07PM +0100, Radoslaw Burny wrote:
>> Due to a recent commit (d151ddc00498 - fs: Update i_[ug]id_(read|write)
>> to translate relative to s_user_ns),
>
> Recent? This is commit is from 2014 and present upstream since v4.8.
> And the commit
On Mon, Nov 26, 2018 at 06:26:07PM +0100, Radoslaw Burny wrote:
> Due to a recent commit (d151ddc00498 - fs: Update i_[ug]id_(read|write)
> to translate relative to s_user_ns),
Recent? This is commit is from 2014 and present upstream since v4.8.
And the commit ID you mentioned in your commit log
On Mon, Nov 26, 2018 at 06:26:07PM +0100, Radoslaw Burny wrote:
> Due to a recent commit (d151ddc00498 - fs: Update i_[ug]id_(read|write)
> to translate relative to s_user_ns),
Recent? This is commit is from 2014 and present upstream since v4.8.
And the commit ID you mentioned in your commit log
Due to a recent commit (d151ddc00498 - fs: Update i_[ug]id_(read|write)
to translate relative to s_user_ns), inodes under /proc/sys have -1
written to their i_uid/i_gid members if a containing userns does not
have entries for root in the uid/gid_map.
This wouldn't normally matter, because these
Due to a recent commit (d151ddc00498 - fs: Update i_[ug]id_(read|write)
to translate relative to s_user_ns), inodes under /proc/sys have -1
written to their i_uid/i_gid members if a containing userns does not
have entries for root in the uid/gid_map.
This wouldn't normally matter, because these
16 matches
Mail list logo
