All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: pNFS Mailing List <pnfs@linux-nfs.org>,
	"J. Bruce Fields" <bfields@citi.umich.edu>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Doug Nazar <nazard.lkml@gmail.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [pnfs] [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT case to use of do_last()
Date: Thu, 25 Mar 2010 13:13:51 +0200	[thread overview]
Message-ID: <4BAB456F.7080501@panasas.com> (raw)
In-Reply-To: <4BAB4523.1010601@panasas.com>

On Mar. 25, 2010, 13:12 +0200, Benny Halevy <bhalevy@panasas.com> wrote:
> On Mar. 25, 2010, 13:00 +0200, Al Viro <viro@ZenIV.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@linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs

  reply	other threads:[~2010-03-25 11:13 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 15:49 [GIT BISECT] first bad commit: 1f36f774 Switch !O_CREAT case to use of do_last() Boaz Harrosh
2010-03-24 15:49 ` Boaz Harrosh
2010-03-24 16:00 ` Al Viro
2010-03-24 16:04   ` Boaz Harrosh
2010-03-24 16:07     ` Al Viro
2010-03-24 16:10       ` Boaz Harrosh
2010-03-24 16:39         ` Al Viro
2010-03-24 17:15           ` Boaz Harrosh
2010-03-24 17:32             ` [pnfs] " Boaz Harrosh
2010-03-24 17:47               ` Boaz Harrosh
2010-03-24 17:58                 ` Boaz Harrosh
2010-03-24 18:06                   ` Al Viro
2010-03-24 18:26                     ` Doug Nazar
2010-03-24 18:56                       ` Al Viro
2010-03-25  9:39                         ` Boaz Harrosh
2010-03-25 10:12                           ` Al Viro
2010-03-25 10:22                             ` Benny Halevy
2010-03-25 10:31                               ` Benny Halevy
2010-03-25 10:49                               ` Al Viro
2010-03-25 10:56                                 ` Benny Halevy
2010-03-25 11:00                                   ` Al Viro
2010-03-25 11:12                                     ` Benny Halevy
2010-03-25 11:13                                       ` Benny Halevy [this message]
2010-03-25 11:55                                 ` Al Viro
2010-03-25 13:00                                   ` Boaz Harrosh
2010-03-25 13:11                                     ` Boaz Harrosh
2010-03-25 10:54                             ` Al Viro
2010-03-25 11:19                               ` Benny Halevy
2010-03-25 12:07                               ` Benny Halevy
2010-03-25 12:18                                 ` Benny Halevy
2010-03-25 13:06                                   ` Al Viro
2010-03-25 13:30                                     ` Boaz Harrosh
2010-03-25 13:37                                       ` Al Viro
2010-03-25 13:45                                         ` Boaz Harrosh
2010-03-25 14:04                                           ` Al Viro
2010-03-25 14:27                                             ` Boaz Harrosh
2010-03-25 15:25                                               ` Al Viro
2010-03-25 17:28                                                 ` Boaz Harrosh
2010-03-25 17:59                                                   ` Trond Myklebust
2010-03-25 18:06                                                     ` Boaz Harrosh
2010-03-25 18:18                                                       ` Trond Myklebust
2010-03-25 18:33                                                         ` Boaz Harrosh
2010-03-25 13:52                                         ` Benny Halevy
2010-03-25 14:06                                           ` Al Viro
2010-03-25 14:07                                             ` Benny Halevy
2010-03-25 14:36                                               ` Benny Halevy
2010-03-24 18:02                 ` Trond Myklebust
2010-03-24 18:10                   ` Trond Myklebust
2010-03-25  9:13                     ` Boaz Harrosh
2010-03-25 15:44                       ` Trond Myklebust
2010-03-25 10:11                     ` Benny Halevy

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=4BAB456F.7080501@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bfields@citi.umich.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nazard.lkml@gmail.com \
    --cc=pnfs@linux-nfs.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.