From: Chen Yu <yu.c.chen@intel.com>
To: Pavan Kondeti <quic_pkondeti@quicinc.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <len.brown@intel.com>, 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: Thu, 6 Apr 2023 10:42:50 +0800 [thread overview]
Message-ID: <ZC4xqolqS51M9dEH@chenyu5-mobl1> (raw)
In-Reply-To: <20230405070000.GA720822@hu-pkondeti-hyd.qualcomm.com>
Hi Pavan,
On 2023-04-05 at 12:30:00 +0530, Pavan Kondeti wrote:
> On Sun, Apr 02, 2023 at 12:55:40AM +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>
> > +int swsusp_check(bool safe)
> > {
> > + fmode_t mode = FMODE_READ;
> > int error;
> > void *holder;
> >
> > + if (!safe)
> > + mode |= FMODE_EXCL;
> > +
> > hib_resume_bdev = blkdev_get_by_dev(swsusp_resume_device,
> > - FMODE_READ | FMODE_EXCL, &holder);
> > + mode, &holder);
> > if (!IS_ERR(hib_resume_bdev)) {
> > set_blocksize(hib_resume_bdev, PAGE_SIZE);
> > clear_page(swsusp_header);
> > @@ -1547,7 +1551,7 @@ int swsusp_check(void)
> >
> > put:
> > if (error)
> > - blkdev_put(hib_resume_bdev, FMODE_READ | FMODE_EXCL);
> > + blkdev_put(hib_resume_bdev, mode);
> > else
> > pr_debug("Image signature found, resuming\n");
> > } else {
>
> The patch looks good to me and it works. I have just one
> question/comment.
>
> What is "safe" here? Because I worked on this problem [1], so I
> understood it. but it is not very clear / explicit.
I see.
> One approach I thought would be to the codepaths aware of "test_resume" via a
> global variable called "snapshot_testing" similar to freezer_test_done.
> if snapshot_testing is true, don't use exclusive flags.
This looks reasonable, with this change, we don't have to add "safe" parameter to
swsusp_check() and load_image_and_restore().
thanks,
Chenyu
>
> Thanks,
> Pavan
>
next prev parent reply other threads:[~2023-04-06 2:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 16:55 [PATCH] PM: hibernate: Do not get block device exclusively in test_resume mode Chen Yu
2023-04-05 7:00 ` Pavan Kondeti
2023-04-06 2:42 ` Chen Yu [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-04-03 8:05 Wang, Wendy
2023-04-01 15:48 Chen Yu
2023-04-01 8:03 ` Chen Yu
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=ZC4xqolqS51M9dEH@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=quic_pkondeti@quicinc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox