[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201405241729.AEI35937.HFFQJOOFLOVMSt@I-love.SAKURA.ne.jp>
Date: Sat, 24 May 2014 17:29:35 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: miklos@...redi.hu, linux-security-module@...r.kernel.org
Cc: viro@...IV.linux.org.uk, torvalds@...ux-foundation.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
hch@...radead.org, akpm@...ux-foundation.org, apw@...onical.com,
nbd@...nwrt.org, neilb@...e.de, jordipujolp@...il.com,
ezk@....cs.sunysb.edu, dhowells@...hat.com, sedat.dilek@...il.com,
hooanon05@...oo.co.jp, mszeredi@...e.cz
Subject: Re: [PATCH 06/13] vfs: add whiteout support
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@...r.kernel.org when making VFS changes.
TOMOYO and AppArmor don't want to be left behind again.)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists