diff options
author | Evan Green <evgreen@chromium.org> | 2021-10-29 12:24:22 -0700 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2021-11-24 13:50:18 +0100 |
commit | 88a5045f176b78c33a269a30a7b146e99c550bd9 (patch) | |
tree | e78632648e4ddf27ff86e44116cf764ad9b400ed /kernel/utsname.c | |
parent | cefcf24b4d351daf70ecd945324e200d3736821e (diff) | |
download | linux-88a5045f176b78c33a269a30a7b146e99c550bd9.tar.gz linux-88a5045f176b78c33a269a30a7b146e99c550bd9.tar.bz2 linux-88a5045f176b78c33a269a30a7b146e99c550bd9.zip |
PM: hibernate: Fix snapshot partial write lengths
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>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'kernel/utsname.c')
0 files changed, 0 insertions, 0 deletions