public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Evan Green <evgreen@chromium.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH] PM / hibernate: Fix snapshot partial write lengths
Date: Tue, 30 Nov 2021 07:51:36 +0100	[thread overview]
Message-ID: <YaXJ+LqbmlKJ21Ja@kroah.com> (raw)
In-Reply-To: <CAE=gft6o0JxhDgazPA5DVbL6hQ+36D_GkzgN-AuR3YA43NSqaw@mail.gmail.com>

On Mon, Nov 29, 2021 at 08:50:06AM -0800, Evan Green wrote:
> On Wed, Nov 24, 2021 at 4:54 AM Rafael J. Wysocki <rafael@kernel.org> wrote:
> >
> > On Tue, Nov 16, 2021 at 9:22 PM Evan Green <evgreen@chromium.org> wrote:
> > >
> > > On Tue, Nov 16, 2021 at 9:54 AM Rafael J. Wysocki <rafael@kernel.org> wrote:
> > > >
> > > > On Mon, Nov 15, 2021 at 6:13 PM Evan Green <evgreen@chromium.org> wrote:
> > > > >
> > > > > Gentle bump.
> > > > >
> > > > >
> > > > > On Fri, Oct 29, 2021 at 12:24 PM Evan Green <evgreen@chromium.org> wrote:
> > > > > >
> > > > > > snapshot_write() is inappropriately limiting the amount of data that can
> > > > > > be written in cases where a partial page has already been written. For
> > > > > > example, one would expect to be able to write 1 byte, then 4095 bytes to
> > > > > > the snapshot device, and have both of those complete fully (since now
> > > > > > we're aligned to a page again). But what ends up happening is we write 1
> > > > > > byte, then 4094/4095 bytes complete successfully.
> > > > > >
> > > > > > The reason is that simple_write_to_buffer()'s second argument is the
> > > > > > total size of the buffer, not the size of the buffer minus the offset.
> > > > > > Since simple_write_to_buffer() accounts for the offset in its
> > > > > > implementation, snapshot_write() can just pass the full page size
> > > > > > directly down.
> > > > > >
> > > > > > Signed-off-by: Evan Green <evgreen@chromium.org>
> > > > > > ---
> > > > > >
> > > > > >  kernel/power/user.c | 2 +-
> > > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > >
> > > > > > diff --git a/kernel/power/user.c b/kernel/power/user.c
> > > > > > index 740723bb388524..ad241b4ff64c58 100644
> > > > > > --- a/kernel/power/user.c
> > > > > > +++ b/kernel/power/user.c
> > > > > > @@ -177,7 +177,7 @@ static ssize_t snapshot_write(struct file *filp, const char __user *buf,
> > > > > >                 if (res <= 0)
> > > > > >                         goto unlock;
> > > > > >         } else {
> > > > > > -               res = PAGE_SIZE - pg_offp;
> > > > > > +               res = PAGE_SIZE;
> > > > > >         }
> > > > > >
> > > > > >         if (!data_of(data->handle)) {
> > > > > > --
> > > >
> > > > Do you actually see this problem in practice?
> > >
> > > Yes. I may fire up another thread to explain why I'm stuck doing a
> > > partial page write, and how I might be able to stop doing that in the
> > > future with some kernel help. But either way, this is a bug.
> >
> > OK, patch applied as 5.16-rc material.
> >
> > I guess it should go into -stable kernels too?
> 
> Yes, putting it into -stable would make sense also. I should have CCed
> them originally, doing that now.


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  reply	other threads:[~2021-11-30  6:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 19:24 [PATCH] PM / hibernate: Fix snapshot partial write lengths Evan Green
2021-11-15 17:12 ` Evan Green
2021-11-16 17:54   ` Rafael J. Wysocki
2021-11-16 20:22     ` Evan Green
2021-11-24 12:54       ` Rafael J. Wysocki
2021-11-29 16:50         ` Evan Green
2021-11-30  6:51           ` Greg KH [this message]
2021-11-30 11:46           ` Rafael J. Wysocki
2021-11-30 17:44             ` Evan Green

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=YaXJ+LqbmlKJ21Ja@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=evgreen@chromium.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    /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