From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Zakaria ElQotbi <zakaria.elqotbi@redbend.com>
Cc: miklos@szeredi.hu, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] overlayfs: copyup security inode field
Date: Thu, 20 Mar 2014 14:17:13 +0900 [thread overview]
Message-ID: <3324.1395292633@jrobl> (raw)
In-Reply-To: <20140319152007.GF7642@w-fr-zakariae>
Zakaria ElQotbi:
> I think this field must be the same as the underlying filesystem, instead of
> creating new fresh one at ovl_new_inode() which give an UNLABELED sid.
When two inodes refers to a single inode_security_struct (i_security),
won't it cause a "double free" problem?
J. R. Okajima
next prev parent reply other threads:[~2014-03-20 5:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 15:20 [PATCH] overlayfs: copyup security inode field Zakaria ElQotbi
2014-03-20 5:17 ` J. R. Okajima [this message]
2014-03-26 19:00 ` Zakaria ElQotbi
2014-03-27 4:58 ` J. R. Okajima
2014-04-09 17:14 ` Zakaria ElQotbi
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=3324.1395292633@jrobl \
--to=hooanon05g@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=zakaria.elqotbi@redbend.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.