Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: bjoern <bjoern-6mE/F8KvGsCzQB+pC5nmwQ@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Strange hardlink behavior with CIFS
Date: Wed, 20 Oct 2010 09:18:40 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101020T111137-239@post.gmane.org> (raw)
In-Reply-To: 4CBD6843.3060702@suse.de


> 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?

I had this problem on 2.6.32.
I just gave 2.6.36-rc4 a spin and I can't reproduce this issue anymore with the
new kernel. So, all-clear at least from my side.

Reagrds
Björn 

  reply	other threads:[~2010-10-20  9:18 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 [this message]
     [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
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=loom.20101020T111137-239@post.gmane.org \
    --to=bjoern-6me/f8kvgsczqb+pc5nmwq@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@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