From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: miklos@szeredi.hu, linux-security-module@vger.kernel.org
Cc: viro@ZenIV.linux.org.uk, torvalds@linux-foundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@infradead.org, akpm@linux-foundation.org, apw@canonical.com,
nbd@openwrt.org, neilb@suse.de, jordipujolp@gmail.com,
ezk@fsl.cs.sunysb.edu, dhowells@redhat.com,
sedat.dilek@gmail.com, hooanon05@yahoo.co.jp, mszeredi@suse.cz
Subject: Re: [PATCH 06/13] vfs: add whiteout support
Date: Sat, 24 May 2014 17:29:35 +0900 [thread overview]
Message-ID: <201405241729.AEI35937.HFFQJOOFLOVMSt@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <1400838223-30844-7-git-send-email-miklos@szeredi.hu>
Miklos Szeredi wrote:
> +int vfs_whiteout(struct inode *dir, struct dentry *dentry)
> +{
> + int error = may_create(dir, dentry);
> + if (error)
> + return error;
> +
> + if (!dir->i_op->mknod)
> + return -EPERM;
> +
> + return dir->i_op->mknod(dir, dentry,
> + S_IFCHR | WHITEOUT_MODE, WHITEOUT_DEV);
> +}
> +EXPORT_SYMBOL(vfs_whiteout);
May I verify which/how security_path_*() hooks are called for vfs_whiteout() ?
(Please include linux-security-module@vger.kernel.org when making VFS changes.
TOMOYO and AppArmor don't want to be left behind again.)
next prev parent reply other threads:[~2014-05-24 8:31 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 9:43 [PATCH 00/13] overlay filesystem v22 Miklos Szeredi
2014-05-23 9:43 ` [PATCH 01/13] vfs: add i_op->dentry_open() Miklos Szeredi
2014-05-23 9:43 ` [PATCH 02/13] vfs: export do_splice_direct() to modules Miklos Szeredi
2014-05-23 9:43 ` [PATCH 03/13] vfs: export __inode_permission() " Miklos Szeredi
2014-05-23 9:43 ` [PATCH 04/13] vfs: introduce clone_private_mount() Miklos Szeredi
2014-05-23 9:43 ` [PATCH 05/13] vfs: export check_sticky() Miklos Szeredi
2014-05-23 9:43 ` [PATCH 06/13] vfs: add whiteout support Miklos Szeredi
2014-05-24 8:29 ` Tetsuo Handa [this message]
2014-05-23 9:43 ` [PATCH 07/13] vfs: add RENAME_WHITEOUT Miklos Szeredi
2014-05-24 8:02 ` Azat Khuzhin
2014-05-23 9:43 ` [PATCH 08/13] overlay filesystem Miklos Szeredi
2014-05-23 9:43 ` [PATCH 09/13] overlayfs: add statfs support Miklos Szeredi
2014-05-23 9:43 ` [PATCH 10/13] overlayfs: implement show_options Miklos Szeredi
2014-05-23 9:43 ` [PATCH 11/13] overlay: overlay filesystem documentation Miklos Szeredi
2014-05-23 9:43 ` [PATCH 12/13] fs: limit filesystem stacking depth Miklos Szeredi
2014-05-23 9:43 ` [PATCH 13/13] vfs: dcache: Export d_ancestor to modules Miklos Szeredi
2014-05-26 1:56 ` [PATCH 00/13] overlay filesystem v22 J. R. Okajima
2014-05-28 16:06 ` Miklos Szeredi
2014-05-29 10:26 ` David Howells
2014-05-29 11:26 ` Miklos Szeredi
2014-05-29 10:54 ` Kernel errors with " David Howells
2014-05-29 11:16 ` David Howells
2014-05-29 11:28 ` David Howells
2014-05-29 12:07 ` Miklos Szeredi
2014-05-29 16:06 ` Miklos Szeredi
2014-05-29 16:10 ` Sedat Dilek
2014-05-29 16:23 ` More kernel " David Howells
2014-05-29 16:36 ` Miklos Szeredi
2014-05-29 16:44 ` David Howells
2014-05-29 16:48 ` Unionmount and overlayfs testsuite David Howells
2014-05-29 17:11 ` Sedat Dilek
2014-05-29 17:15 ` David Howells
2014-05-29 17:19 ` Sedat Dilek
2014-05-29 17:24 ` David Howells
2014-05-29 17:36 ` Sedat Dilek
2014-05-29 17:41 ` David Howells
2014-05-29 17:44 ` Sedat Dilek
2014-05-29 18:22 ` David Howells
2014-05-29 18:44 ` Sedat Dilek
2014-05-29 18:53 ` Sedat Dilek
2014-05-29 19:20 ` David Howells
2014-05-29 19:24 ` Sedat Dilek
2014-05-29 19:25 ` David Howells
2014-05-29 19:28 ` Sedat Dilek
2014-05-29 19:35 ` David Howells
2014-05-29 20:00 ` Sedat Dilek
2014-05-29 20:59 ` David Howells
2014-05-30 4:15 ` Sedat Dilek
2014-05-30 4:29 ` Sedat Dilek
2014-05-30 7:54 ` David Howells
2014-05-29 17:35 ` Sedat Dilek
2014-05-29 17:50 ` David Howells
2014-05-29 17:58 ` Sedat Dilek
2014-05-29 18:23 ` Dave Jones
2014-05-29 18:27 ` David Howells
2014-05-29 17:17 ` David Howells
2014-05-29 23:21 ` Dave Chinner
2014-05-30 3:35 ` J. R. Okajima
2014-05-30 4:44 ` J. R. Okajima
2014-05-30 8:49 ` David Howells
2014-05-30 9:15 ` J. R. Okajima
2014-06-03 8:08 ` Sedat Dilek
2014-06-03 9:00 ` David Howells
2014-06-03 9:12 ` Miklos Szeredi
2014-06-03 9:18 ` Sedat Dilek
2014-06-03 9:26 ` Sedat Dilek
2014-06-03 9:39 ` Sedat Dilek
2014-06-03 9:42 ` Miklos Szeredi
2014-06-03 10:15 ` Sedat Dilek
2014-06-03 10:21 ` Sedat Dilek
2014-06-03 10:55 ` Sedat Dilek
2014-06-03 10:33 ` David Howells
2014-06-03 13:21 ` Miklos Szeredi
2014-06-03 14:26 ` Sedat Dilek
2014-06-03 15:30 ` David Howells
2014-06-03 15:53 ` Miklos Szeredi
2014-06-05 22:16 ` David Howells
2014-06-24 16:46 ` Overlayfs rename bug David Howells
2014-07-08 9:29 ` Miklos Szeredi
2014-07-08 9:56 ` David Howells
2014-07-09 14:14 ` Miklos Szeredi
2014-05-30 9:14 ` Unionmount and overlayfs testsuite David Howells
2014-05-29 17:29 ` Kernel errors with overlay filesystem v22 David Howells
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=201405241729.AEI35937.HFFQJOOFLOVMSt@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dhowells@redhat.com \
--cc=ezk@fsl.cs.sunysb.edu \
--cc=hch@infradead.org \
--cc=hooanon05@yahoo.co.jp \
--cc=jordipujolp@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@suse.cz \
--cc=nbd@openwrt.org \
--cc=neilb@suse.de \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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.