linux-kernel - Re: linux-next: build failure after merge of the akpm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120625164049.GO5042@outflux.net>
Date:	Mon, 25 Jun 2012 09:40:49 -0700
From:	Kees Cook <keescook@...omium.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Kees Cook <keescook@...omium.org>,
	Al Viro <viro@...IV.linux.org.uk>,
	Miklos Szeredi <mszeredi@...e.cz>
Subject: Re: linux-next: build failure after merge of the akpm tree

Hi Stephen,

On Mon, Jun 25, 2012 at 04:41:41PM +1000, Stephen Rothwell wrote:
> After merging the akpm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> fs/namei.c: In function 'path_openat':
> fs/namei.c:2874:4: error: 'filp' undeclared (first use in this function)
> 
> Caused by patch "fs: add link restrictions" from the akpm tree
> interacting with (at least) commit 4066cd545681 ("vfs: remove open
> intents from nameidata") from the vfs tree.
> 
> I don't know how to fix this, so I have reverted the akpm patch for today
> (in the hope that someone else will fix it).

It looks like namei.c changed the logic of the lookup loop. This should
fix it.

Signed-off-by: Kees Cook <keescook@...omium.org>

---

diff -uNrp a/fs/namei.c b/fs/namei.c
--- a/fs/namei.c	2012-06-25 09:30:28.125746562 -0700
+++ b/fs/namei.c	2012-06-25 09:31:29.456997558 -0700
@@ -2870,10 +2870,8 @@ static struct file *path_openat(int dfd,
 			break;
 		}
 		error = may_follow_link(&link);
-		if (unlikely(error)) {
-			filp = ERR_PTR(error);
+		if (unlikely(error))
 			break;
-		}
 		nd->flags |= LOOKUP_PARENT;
 		nd->flags &= ~(LOOKUP_OPEN|LOOKUP_CREATE|LOOKUP_EXCL);
 		error = follow_link(&link, nd, &cookie);


-- 
Kees Cook
Chrome OS Security
--
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/