From: Matt Mackall <mpm-VDJrAJ4Gl5ZBDgjK7y7TUQ@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Strange hardlink behavior with CIFS
Date: Wed, 27 Oct 2010 15:49:10 -0500 [thread overview]
Message-ID: <1288212550.3764.59.camel@calx> (raw)
In-Reply-To: <20101027163230.28591971-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
On Wed, 2010-10-27 at 16:32 -0400, Jeff Layton wrote:
> On Wed, 27 Oct 2010 12:31:26 -0500
> Matt Mackall <mpm-VDJrAJ4Gl5ZBDgjK7y7TUQ@public.gmane.org> wrote:
>
> > On Tue, 2010-10-19 at 15:13 +0530, Suresh Jayaraman wrote:
> > > On 10/19/2010 12:34 AM, Matt Mackall wrote:
> > > > With Linux 2.6.32-35 and either Windows or Samba in nounix mode,
> > > > hardlink counts can mysteriously disappear:
> > > >
> > > > - create hardlink pair foo,bar
> > > > - stat foo -> nlink = 2
> > > > - open foo
> > > > - stat foo -> nlink = 1
> > > > - close
> > > > - wait or sync
> > > > - ls -l -> nlink = 2
> > > >
> > > > Original report is here:
> > > >
> > > > http://mercurial.selenic.com/bts/issue1866
> > > >
> > >
> > > A quick test on 2.6.36-rc4 kernel reveals that the problem is no longer
> > > reproducible. Could you try a more recent kernel and see whether the
> > > problem is reproducible?
> >
> > Test continues to fail with 2.6.36.
> >
> > # uname -a
> > Linux calx 2.6.36 #71 SMP Tue Oct 26 02:23:34 CDT 2010 x86_64 GNU/Linux
> > # mount -o nounix //localhost/stuff cifs
> > ^^^^^^
> > # cd cifs
> > # touch foo
> > # ln foo bar
> > # ./h
> > file: foo nlinks 2
> > file: foo nlinks 1
> > file: foo nlinks 1
> >
> > # cat h.c
> > #include <sys/types.h>
> > #include <sys/stat.h>
> > #include <unistd.h>
> > #include <fcntl.h>
> > #include <stdio.h>
> >
> > #define FPATH "foo"
> >
> > int main(void)
> > {
> > int rc, fh;
> > struct stat st;
> >
> > rc = lstat(FPATH, &st);
> > printf("file: %s nlinks %d\n", FPATH, st.st_nlink);
> >
> > fh = open(FPATH, 0, O_RDONLY);
> >
> > rc = lstat(FPATH, &st);
> > printf("file: %s nlinks %d\n", FPATH, st.st_nlink);
> >
> > close(fh);
> >
> > rc = lstat(FPATH, &st);
> > printf("file: %s nlinks %d\n", FPATH, st.st_nlink);
> >
> > return 0;
> > }
> >
> >
> >
> >
>
> Ok, I can reproduce this too. The problem is this nastiness in CIFSSMBOpen:
>
> if (rc) {
> cFYI(1, "Error in Open = %d", rc);
> } else {
> *pOplock = pSMBr->OplockLevel; /* 1 byte no need to le_to_cpu */
> *netfid = pSMBr->Fid; /* cifs fid stays in le */
> /* Let caller know file was created so we can set the mode. */
> /* Do we care about the CreateAction in any other cases? */
> if (cpu_to_le32(FILE_CREATE) == pSMBr->CreateAction)
> *pOplock |= CIFS_CREATE_ACTION;
> if (pfile_info) {
> memcpy((char *)pfile_info, (char *)&pSMBr->CreationTime,
> 36 /* CreationTime to Attributes */);
> /* the file_info buf is endian converted by caller */
> pfile_info->AllocationSize = pSMBr->AllocationSize;
> pfile_info->EndOfFile = pSMBr->EndOfFile;
> pfile_info->NumberOfLinks = cpu_to_le32(1);
> pfile_info->DeletePending = 0;
> }
> }
>
> In particular, the NumberOfLinks being set to 1 there. That probably
> just needs to go. I'll look over it when I have time.
I should have noted that the behavior is* different be .35 and .36 - the
link count reappears quite quickly after the test in .36 so a manual
test is unlikely to show the problem now. But back-to-back close/stat
still shows the problem.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2010-10-27 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 19:04 Strange hardlink behavior with CIFS Matt Mackall
2010-10-19 9:43 ` Suresh Jayaraman
2010-10-20 9:18 ` bjoern
[not found] ` <loom.20101020T111137-239-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2010-10-20 15:01 ` Steve French
[not found] ` <4CBD6843.3060702-l3A5Bk7waGM@public.gmane.org>
2010-10-27 17:31 ` Matt Mackall
2010-10-27 20:32 ` Jeff Layton
[not found] ` <20101027163230.28591971-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-10-27 20:49 ` Matt Mackall [this message]
2010-10-28 11:08 ` Suresh Jayaraman
[not found] ` <4CC959AC.10301-l3A5Bk7waGM@public.gmane.org>
2010-10-28 11:46 ` Jeff Layton
[not found] ` <20101028074650.3e035241-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-10-29 10:51 ` Suresh Jayaraman
[not found] ` <4CCAA73D.80009-l3A5Bk7waGM@public.gmane.org>
2010-10-29 11:19 ` Jeff Layton
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=1288212550.3764.59.camel@calx \
--to=mpm-vdjraj4gl5zbdgjk7y7tuq@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjayaraman-l3A5Bk7waGM@public.gmane.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