From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, "J. R. Okajima" <hooanon05@yahoo.co.jp>
Subject: [RFC Aufs2 #2 20/28] aufs ioctl
Date: Mon, 16 Mar 2009 16:20:32 +0900 [thread overview]
Message-ID: <1237188040-11404-21-git-send-email-hooanon05@yahoo.co.jp> (raw)
In-Reply-To: <1237188040-11404-1-git-send-email-hooanon05@yahoo.co.jp>
initial commit
currently for maintenance only
Signed-off-by: J. R. Okajima <hooanon05@yahoo.co.jp>
---
fs/aufs/ioctl.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 54 insertions(+), 0 deletions(-)
create mode 100644 fs/aufs/ioctl.c
diff --git a/fs/aufs/ioctl.c b/fs/aufs/ioctl.c
new file mode 100644
index 0000000..ff17d77
--- /dev/null
+++ b/fs/aufs/ioctl.c
@@ -0,0 +1,54 @@
+/*
+ * Copyright (C) 2005-2009 Junjiro R. Okajima
+ *
+ * This program, aufs is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ */
+
+#include <linux/uaccess.h>
+#include "aufs.h"
+
+long aufs_ioctl_dir(struct file *file, unsigned int cmd,
+ unsigned long arg __maybe_unused)
+{
+ long err;
+ struct super_block *sb;
+ struct au_sbinfo *sbinfo;
+
+ err = -EACCES;
+ if (!capable(CAP_SYS_ADMIN))
+ goto out;
+
+ err = 0;
+ sb = file->f_dentry->d_sb;
+ sbinfo = au_sbi(sb);
+ switch (cmd) {
+ case AUFS_CTL_PLINK_MAINT:
+ /*
+ * pseudo-link maintenance mode,
+ * cleared by aufs_release_dir()
+ */
+ si_write_lock(sb);
+ if (!au_ftest_si(sbinfo, MAINTAIN_PLINK)) {
+ au_fset_si(sbinfo, MAINTAIN_PLINK);
+ au_fi(file)->fi_maintain_plink = 1;
+ } else
+ err = -EBUSY;
+ si_write_unlock(sb);
+ break;
+ case AUFS_CTL_PLINK_CLEAN:
+ if (au_opt_test(sbinfo->si_mntflags, PLINK)) {
+ aufs_write_lock(sb->s_root);
+ au_plink_put(sb);
+ aufs_write_unlock(sb->s_root);
+ }
+ break;
+ default:
+ err = -EINVAL;
+ }
+
+ out:
+ return err;
+}
--
1.6.1.284.g5dc13
next prev parent reply other threads:[~2009-03-16 7:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 7:20 [RFC Aufs2 #2 00/28] source files J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 01/28] aufs documents J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 02/28] aufs public header file J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 03/28] aufs module global J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 04/28] aufs super_block J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 05/28] aufs branch directory/filesystem J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 06/28] aufs xino J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 07/28] aufs object lifetime management via sysfs J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 08/28] aufs mount options/flags J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 09/28] aufs workqueue J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 10/28] aufs sub-VFS J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 11/28] aufs sub-dcache J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 12/28] aufs copy-up J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 13/28] aufs whiteout J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 14/28] aufs pseudo-link J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 15/28] aufs policies to select one among multiple writable branches J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 16/28] aufs dentry and lookup J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 17/28] aufs file J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 18/28] aufs direcotry J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 19/28] aufs inode J. R. Okajima
2009-03-16 7:20 ` J. R. Okajima [this message]
2009-03-16 7:20 ` [RFC Aufs2 #2 21/28] aufs sysfs entries J. R. Okajima
2009-03-16 18:05 ` Greg KH
2009-03-17 3:26 ` hooanon05
2009-03-17 3:37 ` Greg KH
2009-03-17 4:05 ` hooanon05
2009-03-17 4:22 ` Greg KH
2009-03-17 4:50 ` hooanon05
2009-03-17 10:39 ` Evgeniy Polyakov
2009-03-17 12:56 ` hooanon05
2009-03-19 8:04 ` hooanon05
2009-03-16 7:20 ` [RFC Aufs2 #2 22/28] aufs branch for loopback block device J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 23/28] aufs internal inotify J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 24/28] aufs test for fstype J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 25/28] aufs debug J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 26/28] export splice functions J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 27/28] export lookup functions J. R. Okajima
2009-03-16 7:20 ` [RFC Aufs2 #2 28/28] kbuild aufs J. R. Okajima
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=1237188040-11404-21-git-send-email-hooanon05@yahoo.co.jp \
--to=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®