mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eldad Zack <eldad@fogrefinery.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-scsi@vger.kernel.org, Len Brown <len.brown@intel.com>,
	Meelis Roos <mroos@linux.ee>,
	linux-kernel@vger.kernel.org,
	James Bottomley <JBottomley@parallels.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [set5 PATCH 2/6] async: make async_synchronize_full() flush all work regardless of domain
Date: Fri, 22 Jun 2012 23:40:19 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1206222333050.1141@debianer> (raw)
In-Reply-To: <20120622064707.21538.22198.stgit@dwillia2-linux.jf.intel.com>


On Thu, 21 Jun 2012, Dan Williams wrote:
> In response to an async related regression James noted:
> 
>   "My theory is that this is an init problem: The assumption in a lot of
>    our code is that async_synchronize_full() waits for everything ... even
>    the domain specific async schedules, which isn't true."
> 
> ...so make this assumption true.

Hi Dan,

I've applied the all 6 patches of this set. 
(HEAD 8874e812feb4926f4a51a82c4fca75c7daa05fc5 , Linus' tree)

I've tested it on the same setup and everything runs fine, and I've 
seen no suspicious messages.

If you'd like, I can test only patch #2 in isolation.

Tested-by: Eldad Zack <eldad@fogrefinery.com>

Best regards,
Eldad

  reply	other threads:[~2012-06-22 21:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22  6:46 [set5 PATCH 0/6] scsi, async: asynchronous probing rework / fixes Dan Williams
2012-06-22  6:47 ` [set5 PATCH 1/6] async: introduce 'async_domain' type Dan Williams
2012-06-22  6:47 ` [set5 PATCH 2/6] async: make async_synchronize_full() flush all work regardless of domain Dan Williams
2012-06-22 21:40   ` Eldad Zack [this message]
2012-06-23  7:06     ` Dan Williams
2012-06-22  6:47 ` [set5 PATCH 3/6] scsi: queue async scan work to an async_schedule domain Dan Williams
2012-06-22  6:47 ` [set5 PATCH 4/6] scsi: cleanup usages of scsi_complete_async_scans Dan Williams
2012-06-22  6:47 ` [set5 PATCH 5/6] Revert "[SCSI] fix async probe regression" Dan Williams
2012-06-22  6:47 ` [set5 PATCH 6/6] scsi: fix hot unplug vs async scan race Dan Williams
2012-06-28 22:22 ` [set5 PATCH 0/6] scsi, async: asynchronous probing rework / fixes Dan Williams
2012-06-29  9:06   ` James Bottomley

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=alpine.DEB.2.02.1206222333050.1141@debianer \
    --to=eldad@fogrefinery.com \
    --cc=JBottomley@parallels.com \
    --cc=arjan@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=rjw@sisk.pl \
    /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

Powered by JetHome