public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@wdc.com>
To: "Martin K . Petersen" <martin.petersen@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org, linux-pm@vger.kernel.org,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Woody Suwalski <terraluna977@gmail.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	Bart Van Assche <bart.vanassche@wdc.com>
Subject: [PATCH 0/2] Fix a race condition between SPI domain validation and system suspend
Date: Fri,  5 Jan 2018 09:19:07 -0800	[thread overview]
Message-ID: <20180105171909.11839-1-bart.vanassche@wdc.com> (raw)

Hello Martin,

Recently it was discovered that the v4.15 rework of suspend/resume handling
in the SCSI subsystem introduced a race condition between SPI domain validation
and system suspend. The two patches in this series fix that race. Please
consider these two patches for kernel v4.15.

Thanks,

Bart.

Bart Van Assche (2):
  PM / sleep: Make lock/unlock_system_sleep() available to kernel
    modules
  Fix a race condition between SPI domain validation and system suspend

 drivers/scsi/scsi_transport_spi.c | 16 ++++++++++++++--
 include/linux/suspend.h           | 28 ++--------------------------
 kernel/power/main.c               | 29 +++++++++++++++++++++++++++++
 3 files changed, 45 insertions(+), 28 deletions(-)

-- 
2.15.1

             reply	other threads:[~2018-01-05 17:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 17:19 Bart Van Assche [this message]
2018-01-05 17:19 ` [PATCH 1/2] PM / sleep: Make lock/unlock_system_sleep() available to kernel modules Bart Van Assche
2018-01-05 23:00   ` Rafael J. Wysocki
2018-01-05 23:32     ` Bart Van Assche
2018-01-05 23:38       ` Rafael J. Wysocki
2018-01-05 17:19 ` [PATCH 2/2] Fix a race condition between SPI domain validation and system suspend Bart Van Assche
2018-01-08 16:02   ` Martin K. Petersen
2018-01-09  0:27     ` Rafael J. Wysocki

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=20180105171909.11839-1-bart.vanassche@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=rjw@rjwysocki.net \
    --cc=stern@rowland.harvard.edu \
    --cc=terraluna977@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox