From: Nicolai Stange <nicstange@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jonathan Corbet <corbet@lwn.net>, Jan Kara <jack@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <mmarek@suse.com>,
linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr,
Nicolai Stange <nicstange@gmail.com>
Subject: [PATCH v5 8/8] debugfs: unproxify files created through debugfs_create_u32_array()
Date: Sun, 6 Mar 2016 13:25:03 +0100 [thread overview]
Message-ID: <1457267103-28910-9-git-send-email-nicstange@gmail.com> (raw)
In-Reply-To: <1457267103-28910-1-git-send-email-nicstange@gmail.com>
The struct file_operations u32_array_fops associated with files created
through debugfs_create_u32_array() has been lifetime aware already:
everything needed for subsequent operation is copied to a ->f_private
buffer at file opening time in u32_array_open(). Now, ->open() is always
protected against file removal issues by the debugfs core.
There is no need for the debugfs core to wrap the u32_array_fops
with a file lifetime managing proxy.
Make debugfs_create_u32_array() create its files in non-proxying operation
mode by means of debugfs_create_file_unsafe().
Signed-off-by: Nicolai Stange <nicstange@gmail.com>
---
fs/debugfs/file.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
index 9d4bcd6..6a4b667 100644
--- a/fs/debugfs/file.c
+++ b/fs/debugfs/file.c
@@ -993,7 +993,8 @@ struct dentry *debugfs_create_u32_array(const char *name, umode_t mode,
data->array = array;
data->elements = elements;
- return debugfs_create_file(name, mode, parent, data, &u32_array_fops);
+ return debugfs_create_file_unsafe(name, mode, parent, data,
+ &u32_array_fops);
}
EXPORT_SYMBOL_GPL(debugfs_create_u32_array);
--
2.7.2
prev parent reply other threads:[~2016-03-06 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 12:24 [PATCH v5 0/8] fix debugfs file removal races Nicolai Stange
2016-03-06 12:24 ` [PATCH v5 1/8] debugfs: prevent access to possibly dead file_operations at file open Nicolai Stange
2016-03-10 21:59 ` Rasmus Villemoes
2016-03-11 19:28 ` Nicolai Stange
2016-03-06 12:24 ` [PATCH v5 2/8] debugfs: prevent access to removed files' private data Nicolai Stange
2016-03-06 12:24 ` [PATCH v5 3/8] debugfs: add support for self-protecting attribute file fops Nicolai Stange
2016-03-06 12:24 ` [PATCH v5 4/8] debugfs, coccinelle: check for obsolete DEFINE_SIMPLE_ATTRIBUTE() usage Nicolai Stange
2016-03-06 12:25 ` [PATCH v5 5/8] debugfs: unproxify integer attribute files Nicolai Stange
2016-03-06 12:25 ` [PATCH v5 6/8] debugfs: unproxify files created through debugfs_create_bool() Nicolai Stange
2016-03-06 12:25 ` [PATCH v5 7/8] debugfs: unproxify files created through debugfs_create_blob() Nicolai Stange
2016-03-06 12:25 ` Nicolai Stange [this message]
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=1457267103-28910-9-git-send-email-nicstange@gmail.com \
--to=nicstange@gmail.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=akpm@linux-foundation.org \
--cc=cocci@systeme.lip6.fr \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.fr \
--cc=paulmck@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox