All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Ondrej Zary <linux@rainbow-software.org>,
	Hugh Dickins <hughd@google.com>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>,
	Hans de Bruin <jmdebruin@xmsnet.nl>,
	Linux NFS mailing list <linux-nfs@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	richard -rw- weinberger <richard.weinberger@gmail.com>
Subject: Re: [bisected commit 0fc9d10] NFS-server corruption with 3.4
Date: Tue, 05 Jun 2012 19:03:46 +0200	[thread overview]
Message-ID: <4FCE3BF2.2030608@gmx.de> (raw)
In-Reply-To: <4FCE2CCE.9000900@openvz.org>

On 06/05/2012 05:59 PM, Konstantin Khlebnikov wrote:
> Proper fix in attachment.
> 
That fixes solves the chroot issue I had have - tested at top of
v3.5-rc1-37-g99becf1

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

  parent reply	other threads:[~2012-06-05 17:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05  9:16 [bisected] NFS corruption with 3.4 Ondrej Zary
2012-06-05 12:45 ` Dave Jones
2012-06-05 13:45   ` Holger Hoffstaette
2012-06-05 14:11   ` Ondrej Zary
2012-06-05 13:32 ` [bisected commit 0fc9d10] NFS-server " Konstantin Khlebnikov
2012-06-05 14:20   ` Ondrej Zary
2012-06-05 14:52     ` Konstantin Khlebnikov
2012-06-05 15:07       ` OGAWA Hirofumi
2012-06-05 15:14         ` Konstantin Khlebnikov
2012-06-05 15:59           ` Konstantin Khlebnikov
2012-06-05 16:18             ` OGAWA Hirofumi
2012-06-05 16:39               ` Konstantin Khlebnikov
2012-06-05 22:30                 ` Hans de Bruin
2012-06-06 10:54                   ` Konstantin Khlebnikov
2012-06-05 17:03             ` Toralf Förster [this message]
2012-06-05 17:17               ` Konstantin Khlebnikov
2012-06-06  8:55             ` Ondrej Zary
2012-06-05 14:21   ` Toralf Förster

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=4FCE3BF2.2030608@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=hughd@google.com \
    --cc=jmdebruin@xmsnet.nl \
    --cc=khlebnikov@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    --cc=richard.weinberger@gmail.com \
    /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.