All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Gonzalez Azevedo <rgonzalez@censanet.com.br>
To: Herbert Xu <herbert@gondor.apana.org.au>, xen-devel@lists.xensource.com
Subject: Re: Error with NFS and XEN (High network load)
Date: Thu, 17 Aug 2006 11:09:38 -0300	[thread overview]
Message-ID: <44E478A2.8010708@censanet.com.br> (raw)
In-Reply-To: <20060816160423.GA32653@gondor.apana.org.au>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks !!! Now it's working !!! Dom0 and DomU don't crash anymore !!!
Please, report it on Xen Bugzilla id # 735.


Thanks !

- --
- ----------------------------
Roberto Gonzalez Azevedo


Herbert Xu wrote:
> On Tue, Aug 15, 2006 at 10:58:15PM +0000, Roberto Gonzalez Azevedo wrote:
>> On domU machine:
>> root@domU:# mount -t nfs real-machine-not-xen-or-any-virtual:/mnt /data
>> [ok]
>>
>> Crash:
>> root@domU:# time dd if=/dev/zero of=/data/test.txt bs=16k count=16384
>> [NOT OK]
> 
> Thanks for the report.  This is what I needed to reproduce the problem.
> I forgot to initialise the first fragment to a proper value in the first
> SG patch.
> 
> [NET] back: Initialise first fragment properly
> 
> The first fragment is used to store the pending_idx of the leading
> txreq if it doesn't fit in the head area.  When it does fit into
> the head we need to ensure that the first fragment contains a value
> that is not equal to pending_idx as that's what we use to distinguish
> between the two cases in a a number of places.
> 
> This patch sets the first fragment to ~0 which is not equal to any
> valid pending_idx.  Without this initialisation, we may double-free
> a pending_idx if the first fragment happened to contain a value
> equal to it (this usually happened with pending_idx 0).
> 
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> 
> Cheers,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE5HiiF+EMwkXLsEwRAkGVAKCh4+qOF5ONalGWTSaKYFAQG0/MggCfcLIk
yqtPsCTMxJP7ueouUOCFwkM=
=fuLb
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2006-08-17 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 22:58 Error with NFS and XEN (High network load) Roberto Gonzalez Azevedo
2006-08-16 14:44 ` Emmanuel Ackaouy
2006-08-16 16:18   ` Roberto Gonzalez Azevedo
2006-08-16 16:04 ` Herbert Xu
2006-08-17  3:41   ` Roberto Gonzalez Azevedo
2006-08-17 14:09   ` Roberto Gonzalez Azevedo [this message]

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=44E478A2.8010708@censanet.com.br \
    --to=rgonzalez@censanet.com.br \
    --cc=herbert@gondor.apana.org.au \
    --cc=xen-devel@lists.xensource.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.