mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Casey Dahlin <cjdahlin@ncsu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Code style fix for open_exec
Date: Thu, 4 Oct 2007 08:08:57 +0100	[thread overview]
Message-ID: <20071004070857.GB21481@infradead.org> (raw)
In-Reply-To: <47045299.2000601@ncsu.edu>

On Wed, Oct 03, 2007 at 10:40:25PM -0400, Casey Dahlin wrote:
> From d2a6c5d29dc34cfea892124ab72b4eb55d2f8a80 Mon Sep 17 00:00:00 2001
> From: Casey Dahlin <cjdahlin@ncsu.edu>
> Date: Wed, 3 Oct 2007 22:01:49 -0400
> Subject: [PATCH] Code style fix for open_exec
> 
> Fix a horribly mangled 5 level indent and severe abuse of goto in the 
> open_exec
> function.

While the function is not nice your version makes it even worse.

Try this one instead which has been in my pending testing tree for a while:



Index: linux-2.6/fs/exec.c
===================================================================
--- linux-2.6.orig/fs/exec.c	2007-09-16 20:29:01.000000000 +0200
+++ linux-2.6/fs/exec.c	2007-09-16 20:29:56.000000000 +0200
@@ -669,41 +669,55 @@ EXPORT_SYMBOL(setup_arg_pages);
 
 #endif /* CONFIG_MMU */
 
+/**
+ * open_exec - open file for execution
+ * @name:	filename to open
+ *
+ * Open the file pointed to by @filename in the current namespace
+ * for execution.  Error out if the file is not a regular file or
+ * this mount does not allow executing files on it.
+ */
 struct file *open_exec(const char *name)
 {
 	struct nameidata nd;
-	int err;
 	struct file *file;
+	int err;
 
-	err = path_lookup_open(AT_FDCWD, name, LOOKUP_FOLLOW, &nd, FMODE_READ|FMODE_EXEC);
-	file = ERR_PTR(err);
+	err = path_lookup_open(AT_FDCWD, name, LOOKUP_FOLLOW, &nd,
+				FMODE_READ|FMODE_EXEC);
+	if (unlikely(err))
+		goto out;
 
-	if (!err) {
-		struct inode *inode = nd.dentry->d_inode;
-		file = ERR_PTR(-EACCES);
-		if (!(nd.mnt->mnt_flags & MNT_NOEXEC) &&
-		    S_ISREG(inode->i_mode)) {
-			int err = vfs_permission(&nd, MAY_EXEC);
-			file = ERR_PTR(err);
-			if (!err) {
-				file = nameidata_to_filp(&nd, O_RDONLY);
-				if (!IS_ERR(file)) {
-					err = deny_write_access(file);
-					if (err) {
-						fput(file);
-						file = ERR_PTR(err);
-					}
-				}
-out:
-				return file;
-			}
-		}
-		release_open_intent(&nd);
-		path_release(&nd);
+	err = -EACCES;
+	if (unlikely(nd.mnt->mnt_flags & MNT_NOEXEC))
+		goto out_path_release;
+	if (unlikely(!S_ISREG(nd.dentry->d_inode->i_mode)))
+		goto out_path_release;
+
+	err = vfs_permission(&nd, MAY_EXEC);
+	if (unlikely(err))
+		goto out_path_release;
+
+	file = nameidata_to_filp(&nd, O_RDONLY);
+	if (unlikely(IS_ERR(file))) {
+		err = PTR_ERR(file);
+		goto out;
+	}
+
+	err = deny_write_access(file);
+	if (unlikely(err)) {
+		fput(file);
+		goto out;
 	}
-	goto out;
-}
 
+	return file;
+
+ out_path_release:
+	release_open_intent(&nd);
+	path_release(&nd);
+ out:
+	return ERR_PTR(err);
+}
 EXPORT_SYMBOL(open_exec);
 
 int kernel_read(struct file *file, unsigned long offset,

  reply	other threads:[~2007-10-04  7:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04  2:40 Casey Dahlin
2007-10-04  7:08 ` Christoph Hellwig [this message]
2007-10-04 17:35   ` Casey Dahlin

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=20071004070857.GB21481@infradead.org \
    --to=hch@infradead.org \
    --cc=cjdahlin@ncsu.edu \
    --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®