linux-kernel - Re: [pnfs] [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT case to use of do_last()

Open Source and information security mailing list archives

Message-ID: <4BAB456F.7080501@panasas.com>
Date:	Thu, 25 Mar 2010 13:13:51 +0200
From:	Benny Halevy <bhalevy@...asas.com>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	pNFS Mailing List <pnfs@...ux-nfs.org>,
	"J. Bruce Fields" <bfields@...i.umich.edu>,
	Trond Myklebust <Trond.Myklebust@...app.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Doug Nazar <nazard.lkml@...il.com>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [pnfs] [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT
 case to use of do_last()

On Mar. 25, 2010, 13:12 +0200, Benny Halevy <bhalevy@...asas.com> wrote:
> On Mar. 25, 2010, 13:00 +0200, Al Viro <viro@...IV.linux.org.uk> wrote:
>> On Thu, Mar 25, 2010 at 12:56:40PM +0200, Benny Halevy wrote:
>>> -		if (*want_dir && !path->dentry->d_inode->i_op->lookup)
>>> +		if (*want_dir && !path->dentry->d_inode->i_op->lookup) {
>>> +			WARN_ON(1);
>>>  			goto exit_dput;
>>> +		}
>>>  		path_to_nameidata(path, nd);
>>>  		audit_inode(pathname, nd->path.dentry);
>>>  		goto ok;
>>>
>>> but it is NOT tripping for this scenario.
>>>
>>> (for some reason I saw it tripping when building the kernel over nfs
>>> but it's benign)
>> It's ENOTDIR, not EISDIR, anyway.  Happens if you ask to open foo/ or
>> foo with O_DIRECTORY when foo is not a directory.
> 
> Hmm, not according to my strace (or am I blind today? :)

Duh, you were referring to the hunk I added a WARN_ON to.
Sure. you're right!

> 
>>> open(".git/objects/pack", O_RDONLY|O_NONBLOCK|O_DIRECTORY|0x80000) = -1 EISDIR (Is a directory)
> 
> The odd thing is the app incorrectly gets EISDIR despite
> the fact that it is opening a directory with O_DIRECTORY.
> _______________________________________________
> pNFS mailing list
> pNFS@...ux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
--
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/

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