From: Hans de Bruin <jmdebruin@xmsnet.nl>
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>,
"Linux NFS mailing list" <linux-nfs@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Toralf Förster" <toralf.foerster@gmx.de>,
"richard -rw- weinberger" <richard.weinberger@gmail.com>
Subject: Re: [bisected commit 0fc9d10] NFS-server corruption with 3.4
Date: Wed, 06 Jun 2012 00:30:39 +0200 [thread overview]
Message-ID: <4FCE888F.8050605@xmsnet.nl> (raw)
In-Reply-To: <4FCE3631.9020407@openvz.org>
On 06/05/2012 06:39 PM, Konstantin Khlebnikov wrote:
> OGAWA Hirofumi wrote:
>> Konstantin Khlebnikov<khlebnikov@openvz.org> writes:
>>
>>> Proper fix in attachment.
>>
>> Maybe, you are going to add the stable tag for next stable?
>>
>> Thanks.
>
> Yes, this definitely must be in next stable 3.4.x , but first I'll wait
> for confirmation.
>
> Guys, who can reproduce this, please check patch "radix-tree: fix
> contiguous iterator"
> from my previous mail in this thread.
>
>>
>>> radix-tree: fix contiguous iterator
>>>
>>> From: Konstantin Khlebnikov<khlebnikov@openvz.org>
>>>
>>> This patch fixes bug in macro radix_tree_for_each_contig().
>>> If radix_tree_next_slot() sees NULL in next slot it returns NULL, but
>>> following
>>> radix_tree_next_chunk() switches iterating into next chunk. As result
>>> iterating
>>> becomes non-contiguous and breaks vfs "splice" and all its users.
>>
>
I patched on to off v3.4 and Firefox an Thunderbird do not segfault
anymore. The do not start either. This was de feature on my 'production'
server I could not reproduce on my test server. Maybe it has something
to with the different type of nic's.
For the second attempt I branched of at 0fc9d1040313047edf6a39fd and
applied your patch on top of it. Firefox an Thunderbird where back
again. So your patch works.
Now I need some git-instructions. Apparently something else is broken. I
branched of with:
git branch debug 0fc9d1040313047edf6a3
git checkout debug
applied the patch.
git commit -a (got commit 5c09c685ba2d36c3b905220d43ad1b47354e456eed back)
Now I want all commits in my master branch up until ref v3.4 added to my
debug branch so I can bisect between 5c09 and v3.4
--
Hans
next prev parent reply other threads:[~2012-06-05 23:32 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 [this message]
2012-06-06 10:54 ` Konstantin Khlebnikov
2012-06-05 17:03 ` Toralf Förster
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=4FCE888F.8050605@xmsnet.nl \
--to=jmdebruin@xmsnet.nl \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=hughd@google.com \
--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 \
--cc=toralf.foerster@gmx.de \
/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