On Tue, 2006-09-05 at 12:06 +0800, Ian Kent wrote: > > One way to fix this is to simply not hash the dentry when we're doing > > the O_EXCL intent optimisation, but rather to only hash it _after_ we've > > successfully created the file on the server. Something like the attached > > patch ought to do it. > > No. > > This patch simply marks the dentry negative and returns ENOMEM from the > lookup which, as would be expected, results in this error being returned > to userspace. Oops. You are right. I forgot to set res=NULL...
