From: Laurent Riffard <laurent.riffard@free.fr>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Re: linux-next: reiserfs lockout with xattr ?
Date: Mon, 10 Aug 2009 22:08:26 +0200 [thread overview]
Message-ID: <4A807E3A.8050703@free.fr> (raw)
In-Reply-To: <20090809233302.GD6089@nowhere>
Le 10/08/2009 01:33, Frederic Weisbecker a écrit :
>
> Thanks a lot for this report. Reiserfs xattrs are definetly paths I
> haven't tested deeply.
>
> I'm trying to reproduce these issues and will let you know once I get
> a fix.
>
> (Btw, if you're still running this tree, you should update with the
> latest patch I just pushed, it's a very important fix).
>
> Thanks,
>
> Frederic.
I tried with your lastest patch (git head is at "kill-the-bkl/reiserfs:
fix early readdir offset increment"), and the lockout still happens.
~~
laurent
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Riffard <laurent.riffard@free.fr>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Re: linux-next: reiserfs lockout with xattr ?
Date: Mon, 10 Aug 2009 22:08:26 +0200 [thread overview]
Message-ID: <4A807E3A.8050703@free.fr> (raw)
In-Reply-To: <20090809233302.GD6089@nowhere>
Le 10/08/2009 01:33, Frederic Weisbecker a écrit :
>
> Thanks a lot for this report. Reiserfs xattrs are definetly paths I
> haven't tested deeply.
>
> I'm trying to reproduce these issues and will let you know once I get
> a fix.
>
> (Btw, if you're still running this tree, you should update with the
> latest patch I just pushed, it's a very important fix).
>
> Thanks,
>
> Frederic.
I tried with your lastest patch (git head is at "kill-the-bkl/reiserfs:
fix early readdir offset increment"), and the lockout still happens.
~~
laurent
next prev parent reply other threads:[~2009-08-10 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 18:08 linux-next: reiserfs lockout with xattr ? Laurent Riffard
2009-08-05 18:08 ` Laurent Riffard
2009-08-05 21:43 ` Frederic Weisbecker
2009-08-08 0:27 ` Frederic Weisbecker
2009-08-09 9:52 ` Laurent Riffard
2009-08-09 9:52 ` Laurent Riffard
2009-08-09 23:33 ` Frederic Weisbecker
2009-08-09 23:33 ` Frederic Weisbecker
2009-08-10 20:08 ` Laurent Riffard [this message]
2009-08-10 20:08 ` Laurent Riffard
2009-08-20 14:32 ` Frederic Weisbecker
2009-08-20 14:32 ` Frederic Weisbecker
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=4A807E3A.8050703@free.fr \
--to=laurent.riffard@free.fr \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.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 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.