Linux Power Management development
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Ronald <ronald645@gmail.com>
Cc: linux-kernel@vger.kernel.org, Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: Fwd: [v3.12-rc1] [regression] PM / hibernate: Create memory bitmaps after freezing user space
Date: Tue, 01 Oct 2013 22:35:11 +0200	[thread overview]
Message-ID: <1609889.2pSzhO4Dqr@vostro.rjw.lan> (raw)
In-Reply-To: <CAF1_xX0veXd4AtPR43r50g8Tu4WeP0kVzqPihgSC-NCpW+nwkQ@mail.gmail.com>

On Tuesday, October 01, 2013 06:38:03 PM Ronald wrote:
> This could be a coincidence, but I had a disk data corruption in /var
> (LVM). Most other partitions are read-only during normal operation. So
> I can safely keep testing this kernel. Just mentioning this, in case
> you see this happening with other ppl testing this patch as well.

If you have a failing resume from hibernation a filesystem is perfectly
possible, unfortunately.

The patch itself should't really cause any corruption to happen.

Thanks,
Rafael


> 2013/9/30 Rafael J. Wysocki <rjw@rjwysocki.net>:
> > On Monday, September 30, 2013 07:45:54 AM Ronald wrote:
> >> Yes, works as well. Just survived twe cycles with s2disk. I'm
> >> surprised someone else did not report this earlier btw... Because it
> >> looks pretty generic (i.e. not specific to a 64bit UP system).
> >
> > It is a generic bug, actually.  Well, this means the user space driven
> > hibernation doesn't receive much testing coverage these days ...
> >
> > I'll resend the patch with a proper changelog and then push it for v3.12-rc4.
> >
> > Thanks,
> > Rafael
> >
> >
> >> 2013/9/30 Rafael J. Wysocki <rjw@rjwysocki.net>:
> >> > On Sunday, September 29, 2013 09:22:45 AM Ronald wrote:
> >> >> Attached patch fixes the issue. Both methods function as they did
> >> >> before. Thanks for the superfast fix!
> >> >
> >> > You're welcome, it's not the final one, however.
> >> >
> >> > Can you please test the one below and report back?
> >> >
> >> > Rafael
> >> >
> >> >
> >> > ---
> >> >  kernel/power/snapshot.c |    5 ++++-
> >> >  kernel/power/user.c     |    8 ++++++++
> >> >  2 files changed, 12 insertions(+), 1 deletion(-)
> >> >
> >> > Index: linux-pm/kernel/power/snapshot.c
> >> > ===================================================================
> >> > --- linux-pm.orig/kernel/power/snapshot.c
> >> > +++ linux-pm/kernel/power/snapshot.c
> >> > @@ -743,7 +743,10 @@ int create_basic_memory_bitmaps(void)
> >> >         struct memory_bitmap *bm1, *bm2;
> >> >         int error = 0;
> >> >
> >> > -       BUG_ON(forbidden_pages_map || free_pages_map);
> >> > +       if (forbidden_pages_map && free_pages_map)
> >> > +               return 0;
> >> > +       else
> >> > +               BUG_ON(forbidden_pages_map || free_pages_map);
> >> >
> >> >         bm1 = kzalloc(sizeof(struct memory_bitmap), GFP_KERNEL);
> >> >         if (!bm1)
> >> > Index: linux-pm/kernel/power/user.c
> >> > ===================================================================
> >> > --- linux-pm.orig/kernel/power/user.c
> >> > +++ linux-pm/kernel/power/user.c
> >> > @@ -39,6 +39,7 @@ static struct snapshot_data {
> >> >         char frozen;
> >> >         char ready;
> >> >         char platform_support;
> >> > +       bool free_bitmaps;
> >> >  } snapshot_state;
> >> >
> >> >  atomic_t snapshot_device_available = ATOMIC_INIT(1);
> >> > @@ -82,6 +83,10 @@ static int snapshot_open(struct inode *i
> >> >                 data->swap = -1;
> >> >                 data->mode = O_WRONLY;
> >> >                 error = pm_notifier_call_chain(PM_RESTORE_PREPARE);
> >> > +               if (!error) {
> >> > +                       error = create_basic_memory_bitmaps();
> >> > +                       data->free_bitmaps = !error;
> >> > +               }
> >> >                 if (error)
> >> >                         pm_notifier_call_chain(PM_POST_RESTORE);
> >> >         }
> >> > @@ -111,6 +116,8 @@ static int snapshot_release(struct inode
> >> >                 pm_restore_gfp_mask();
> >> >                 free_basic_memory_bitmaps();
> >> >                 thaw_processes();
> >> > +       } else if (data->free_bitmaps) {
> >> > +               free_basic_memory_bitmaps();
> >> >         }
> >> >         pm_notifier_call_chain(data->mode == O_RDONLY ?
> >> >                         PM_POST_HIBERNATION : PM_POST_RESTORE);
> >> > @@ -231,6 +238,7 @@ static long snapshot_ioctl(struct file *
> >> >                         break;
> >> >                 pm_restore_gfp_mask();
> >> >                 free_basic_memory_bitmaps();
> >> > +               data->free_bitmaps = false;
> >> >                 thaw_processes();
> >> >                 data->frozen = 0;
> >> >                 break;
> >> >
> > --
> > I speak only for myself.
> > Rafael J. Wysocki, Intel Open Source Technology Center.
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2013-10-01 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF1_xX2=BYkEn3ycM4smREqk-ioGbvu8Ea4or22U-jBdKmDKGA@mail.gmail.com>
     [not found] ` <CAF1_xX0suiHSgqWRBrA66qc1A_32Xq08hOikM2VSwQOEgRH-RA@mail.gmail.com>
2013-09-29  1:16   ` Fwd: [v3.12-rc1] [regression] PM / hibernate: Create memory bitmaps after freezing user space Rafael J. Wysocki
2013-09-29  7:22     ` Ronald
2013-09-30  0:12       ` Rafael J. Wysocki
2013-09-30  5:45         ` Ronald
2013-09-30 17:15           ` Rafael J. Wysocki
2013-09-30 17:37             ` [PATCH] PM / hibernate: Fix user space driven resume regression Rafael J. Wysocki
2013-10-01 16:38             ` Fwd: [v3.12-rc1] [regression] PM / hibernate: Create memory bitmaps after freezing user space Ronald
2013-10-01 20:35               ` Rafael J. Wysocki [this message]

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=1609889.2pSzhO4Dqr@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ronald645@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