From: Jonas Meurer <jonas@freesources.org>
To: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Tim Dittler <tim.dittler@systemli.org>,
Yannik Sembritzki <yannik@sembritzki.me>
Subject: [PATCH 0/2] PM: Add a switch for disabling/enabling sync() before suspend
Date: Mon, 2 Dec 2019 18:05:27 +0100 [thread overview]
Message-ID: <1ee5b9ef-f30e-3fde-2325-ba516a96ced5@freesources.org> (raw)
Hello,
Introduce a new run-time sysfs switch to disable/enable sync() before
system suspend. This is useful to avoid races and deadlocks if block
devices have been suspended before, e.g. by 'cryptsetup luksSuspend'.
The second patch changes the behaviour of build-time switch
'CONFIG_SUSPEND_SKIP_SYNC' accordingly, using the build-time switch value
as default for our new run-time switch '/sys/power/sync_on_suspend'.
Jonas Meurer (2):
PM: Add a switch for disabling/enabling sync() before suspend
PM: CONFIG_SUSPEND_SKIP_SYNC sets default for '/sys/power/sync_on_suspend'
Documentation/ABI/testing/sysfs-power | 15 +++++++++++++++
include/linux/suspend.h | 2 ++
kernel/power/Kconfig | 5 ++++-
kernel/power/main.c | 33 +++++++++++++++++++++++++++++++++
kernel/power/suspend.c | 2 +-
5 files changed, 55 insertions(+), 2 deletions(-)
next reply other threads:[~2019-12-02 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 17:05 Jonas Meurer [this message]
2019-12-02 17:07 ` [PATCH 1/2] PM: Add a switch for disabling/enabling sync() before, suspend Jonas Meurer
2019-12-14 9:13 ` Pavel Machek
2019-12-16 16:54 ` Jonas Meurer
2019-12-02 17:07 ` [PATCH 2/2] PM: CONFIG_SUSPEND_SKIP_SYNC sets default for, '/sys/power/sync_on_suspend' Jonas Meurer
2019-12-20 9:35 ` Rafael J. Wysocki
2019-12-20 16:06 ` Jonas Meurer
2019-12-11 15:59 ` [PATCH 0/2] PM: Add a switch for disabling/enabling sync() before suspend Jonas Meurer
2019-12-12 18:00 ` 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=1ee5b9ef-f30e-3fde-2325-ba516a96ced5@freesources.org \
--to=jonas@freesources.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=tim.dittler@systemli.org \
--cc=yannik@sembritzki.me \
/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;
as well as URLs for NNTP newsgroup(s).