From: Serge E. Hallyn Date: Mon, 2 Feb 2009 23:07:33 +0000 (-0800) Subject: securityfs: fix long-broken securityfs_create_file comment X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=faa3aad75a959f55e7783f4dc7840253c7506571;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git securityfs: fix long-broken securityfs_create_file comment If there is an error creating a file through securityfs_create_file, NULL is not returned, rather the error is propagated. Signed-off-by: Serge E. Hallyn Signed-off-by: James Morris --- diff --git a/security/inode.c b/security/inode.c index efea5a605466..b41e708147ae 100644 --- a/security/inode.c +++ b/security/inode.c @@ -205,12 +205,11 @@ static int create_by_name(const char *name, mode_t mode, * This function returns a pointer to a dentry if it succeeds. This * pointer must be passed to the securityfs_remove() function when the file is * to be removed (no automatic cleanup happens if your module is unloaded, - * you are responsible here). If an error occurs, %NULL is returned. + * you are responsible here). If an error occurs, the function will return + * the erorr value (via ERR_PTR). * * If securityfs is not enabled in the kernel, the value %-ENODEV is - * returned. It is not wise to check for this value, but rather, check for - * %NULL or !%NULL instead as to eliminate the need for #ifdef in the calling - * code. + * returned. */ struct dentry *securityfs_create_file(const char *name, mode_t mode, struct dentry *parent, void *data,