From: Chen Yu <yu.c.chen@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Len Brown <len.brown@intel.com>
Cc: Ye Bin <yebin10@huawei.com>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Yifan Li <yifan2.li@intel.com>
Subject: Re: [PATCH] PM: hibernate: Do not get block device exclusively in test_resume mode
Date: Sat, 1 Apr 2023 16:03:35 +0800 [thread overview]
Message-ID: <ZCflV98lGOSIeF88@chenyu5-mobl1> (raw)
In-Reply-To: <20230401154832.320999-1-yu.c.chen@intel.com>
On 2023-04-01 at 23:48:32 +0800, Chen Yu wrote:
> The system refused to do a test_resume because it found that the
> swap device has already been taken by someone else. Specificly,
> the swsusp_check()->blkdev_get_by_dev(FMODE_EXCL) is supposed to
> do this check.
>
> Steps to reproduce:
> dd if=/dev/zero of=/swapfile bs=$(cat /proc/meminfo |
> awk '/MemTotal/ {print $2}') count=1024 conv=notrunc
> mkswap /swapfile
> swapon /swapfile
> swap-offset /swapfile
> echo 34816 > /sys/power/resume_offset
> echo test_resume > /sys/power/disk
> echo disk > /sys/power/state
>
> PM: Using 3 thread(s) for compression
> PM: Compressing and saving image data (293150 pages)...
> PM: Image saving progress: 0%
> PM: Image saving progress: 10%
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: configured for UDMA/100
> ata2: SATA link down (SStatus 0 SControl 300)
> ata5: SATA link down (SStatus 0 SControl 300)
> ata6: SATA link down (SStatus 0 SControl 300)
> ata3: SATA link down (SStatus 0 SControl 300)
> ata4: SATA link down (SStatus 0 SControl 300)
> PM: Image saving progress: 20%
> PM: Image saving progress: 30%
> PM: Image saving progress: 40%
> PM: Image saving progress: 50%
> pcieport 0000:00:02.5: pciehp: Slot(0-5): No device found
> PM: Image saving progress: 60%
> PM: Image saving progress: 70%
> PM: Image saving progress: 80%
> PM: Image saving progress: 90%
> PM: Image saving done
> PM: hibernation: Wrote 1172600 kbytes in 2.70 seconds (434.29 MB/s)
> PM: S|
> PM: hibernation: Basic memory bitmaps freed
> PM: Image not found (code -16)
>
> This is because when using the swapfile as the hibernation storage,
> the block device where the swapfile is located has already been mounted
> by the OS distribution(usually been mounted as the rootfs). This is not
> an issue for normal hibernation, because software_resume()->swsusp_check()
> happens before the block device(rootfs) mount. But it is a problem for the
> test_resume mode. Because when test_resume happens, the block device has
> been mounted already.
>
> Thus remove the FMODE_EXCL for test_resume mode. This would not be a
> problem because in test_resume stage, the processes have already been
> frozen, and the race condition described in
> Commit 39fbef4b0f77 ("PM: hibernate: Get block device exclusively in swsusp_check()")
> is unlikely to happen.
>
> Fixes: 39fbef4b0f77 ("PM: hibernate: Get block device exclusively in swsusp_check()")
> Reported-by: Yifan Li <yifan2.li@intel.com>
> Signed-off-by: Chen Yu <yu.c.chen@intel.com>
>
Please ignore this patch, will send a refined version later. Sorry for the noise.
thanks,
Chenyu
next prev parent reply other threads:[~2023-04-01 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 15:48 [PATCH] PM: hibernate: Do not get block device exclusively in test_resume mode Chen Yu
2023-04-01 8:03 ` Chen Yu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-01 16:55 Chen Yu
2023-04-05 7:00 ` Pavan Kondeti
2023-04-06 2:42 ` Chen Yu
2023-04-05 18:37 ` Rafael J. Wysocki
2023-04-06 2:49 ` Chen Yu
2023-04-06 10:02 ` Rafael J. Wysocki
2023-04-06 11:32 ` Chen Yu
2023-04-09 14:29 ` Chen Yu
2023-04-10 6:52 ` Pavan Kondeti
2023-04-03 8:05 Wang, Wendy
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=ZCflV98lGOSIeF88@chenyu5-mobl1 \
--to=yu.c.chen@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=yebin10@huawei.com \
--cc=yifan2.li@intel.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.