public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nazarov Sergey <s-nazarov@yandex.ru>
To: "Vivek Goyal" <vgoyal@redhat.com>,
	"Ignacy Gawędzki" <ignacy.gawedzki@green-communications.fr>,
	"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] OverlayFS: Fix checking permissions during lookup.
Date: Sat, 27 Feb 2016 13:40:02 +0300	[thread overview]
Message-ID: <419661456569602@web21g.yandex.ru> (raw)
In-Reply-To: <20160226194143.GB13054@redhat.com>

26.02.2016, 22:41, "Vivek Goyal" <vgoyal@redhat.com>:
>
> So what's the problem we are trying to solve. Why should we able to
> override the DAC checks of lower layer if same directory in upper
> is searchable for user but it is not searchable in lower layer.
>

If I right, this is a one of the main feature of overlayfs - upper layer has priority over lower ones.
Override AC checks necessary for lookup operation only. Lower layer files access AC checks
remain, so this should not be a security problem.
Sergey.

  reply	other threads:[~2016-02-27 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 13:55 [PATCH v2 1/1] OverlayFS: Fix checking permissions during lookup Ignacy Gawędzki
2016-02-26 19:41 ` Vivek Goyal
2016-02-27 10:40   ` Nazarov Sergey [this message]
2016-02-29 16:32     ` Vivek Goyal
2016-02-28 11:09   ` Ignacy Gawędzki
2016-02-29 16:25     ` Vivek Goyal
2016-02-29 16:54       ` Ignacy Gawędzki
2016-03-17 15:23         ` Miklos Szeredi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=419661456569602@web21g.yandex.ru \
    --to=s-nazarov@yandex.ru \
    --cc=ignacy.gawedzki@green-communications.fr \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox