All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stodden <daniel.stodden@citrix.com>
To: Xen <xen-devel@lists.xensource.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [PATCH 00 of 10] blkfront pvops updates, v2
Date: Fri, 30 Apr 2010 22:01:14 -0000	[thread overview]
Message-ID: <patchbomb.1272664874@agari.van.xensource.com> (raw)


Updates since the last time:

 * Make sure everything applies against xen/frontend. That fortunately
   made no difference.

 * Two more loopholes:

    - The path freeing info in xenbus_remove took a more carefully
      sync with an unfortunate bdops->release. This is because the
      locking can't just nest. Fixed by resyncing the info pointer
      through disk->private_data.

    - Similar effect during bdev open. This also needs to anticipate
      the not-so-unlikely case where not only the gendisk but the
      entire info struct was deleted just before entry. Again, syncing
      on disk->private_data once holding bd_mutex does the trick.

    I chose to just merge those in.

 * To be honest, that dev_warn the last patch added was broken -- doh.

 * Found the switch [again] for HG to strip those headers -- cheers.

Feedback certainly welcome. I am aware this thing looks manic, but at
it stands, we recently happend to come across exactly that family of
races in XCP again, so I really want these paths fixed.

Thanks,
Daniel

             reply	other threads:[~2010-04-30 22:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30 22:01 Daniel Stodden [this message]
2010-04-30 22:01 ` [PATCH 01 of 10] xenbus: Make xenbus_switch_state transactional (again) Daniel Stodden
2010-04-30 22:01 ` [PATCH 02 of 10] blkfront: Fix backtrace in del_gendisk Daniel Stodden
2010-04-30 22:01 ` [PATCH 03 of 10] blkfront: Fix gendisk leak Daniel Stodden
2010-04-30 22:01 ` [PATCH 04 of 10] blkfront: Clean up vbd release Daniel Stodden
2010-04-30 22:01 ` [PATCH 05 of 10] blkfront: Lock blkfront_info when closing Daniel Stodden
2010-04-30 22:01 ` [PATCH 06 of 10] blkfront: Fix blkfront backend switch race (bdev open) Daniel Stodden
2010-04-30 22:01 ` [PATCH 07 of 10] blkfront: Fix blkfront backend switch race (bdev release) Daniel Stodden
2010-04-30 22:01 ` [PATCH 08 of 10] blkfront: Lock blockfront_info during xbdev removal Daniel Stodden
2010-04-30 22:01 ` [PATCH 09 of 10] blkfront: Remove obsolete info->users Daniel Stodden
2010-04-30 22:01 ` [PATCH 10 of 10] blkfront: Klog the unclean release path Daniel Stodden
2010-04-30 22:16 ` [PATCH 00 of 10] blkfront pvops updates, v2 Jeremy Fitzhardinge
2010-04-30 22:31   ` Daniel Stodden

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=patchbomb.1272664874@agari.van.xensource.com \
    --to=daniel.stodden@citrix.com \
    --cc=jeremy@goop.org \
    --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.