Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1642269
| From | Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 2/2] zram: do not count duplicated pages as compressed |
| Date | 2017-05-16 09:40 +0200 |
| Message-ID | <tHFfk-2DH-13@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <tHzWh-7wv-3@gated-at.bofh.it> <tHAz0-86T-5@gated-at.bofh.it> <tHDdv-1qC-9@gated-at.bofh.it> <tHDwS-1zY-15@gated-at.bofh.it> <tHEVY-2xx-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On (05/16/17 16:16), Minchan Kim wrote:
> > but would this be correct? the data is not valid - we failed to store
> > the valid one. but instead we assure application that read()/swapin/etc.,
> > depending on the usage scenario, is successful (even though the data is
> > not what application really expects to see), application tries to use the
> > data from that page and probably crashes (dunno, for example page contained
> > hash tables with pointers that are not valid anymore, etc. etc.).
> >
> > I'm not optimistic about stale data reads; it basically will look like
> > data corruption to the application.
>
> Hmm, I don't understand what you say.
> My point is zram_free_page should be done only if whoe write operation
> is successful.
> With you change, following situation can happens.
>
> write block 4, 'all A' -> success
> read block 4, 'all A' verified -> Good
> write block 4, 'all B' -> but failed with ENOMEM
> read block 4 expected 'all A' but 'all 0' -> Oops
yes. 'all A' in #4 can be incorrect. zram can be used as a block device
with a file system, and pid that does write op not necessarily does read
op later. it can be a completely different application. e.g. compilation,
or anything else.
suppose PID A does
wr block 1 all a
wr block 2 all a + 1
wr block 3 all a + 2
wr block 4 all a + 3
now PID A does
wr block 1 all m
wr block 2 all m + 1
wr block 3 all m + 2
wr block 4 failed. block still has 'all a + 3'.
exit
another application, PID C, reads in the file and tries to do
something sane with it
rd block 1 all m
rd block 2 all m + 1
rd block 3 all m + 3
rd block 4 all a + 3 << this is dangerous. we should return
error from read() here; not stale data.
what we can return now is a `partially updated' data, with some new
and some stale pages. this is quite unlikely to end up anywhere good.
am I wrong?
why does `rd block 4' in your case causes Oops? as a worst case scenario?
application does not expect page to be 'all A' at this point. pages are
likely to belong to some mappings/files/etc., and there is likely a data
dependency between them, dunno C++ objects that span across pages or
JPEG images, etc. so returning "new data new data stale data" is a bit
fishy.
-ss
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 2/2] zram: do not count duplicated pages as compressed Minchan Kim <minchan@kernel.org> - 2017-05-15 09:50 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-05-16 03:40 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Minchan Kim <minchan@kernel.org> - 2017-05-16 04:00 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-05-16 04:40 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Minchan Kim <minchan@kernel.org> - 2017-05-16 07:30 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-05-16 07:50 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Minchan Kim <minchan@kernel.org> - 2017-05-16 09:20 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-05-16 09:40 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Minchan Kim <minchan@kernel.org> - 2017-05-17 11:00 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-05-17 11:20 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Minchan Kim <minchan@kernel.org> - 2017-05-18 07:00 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Christoph Hellwig <hch@infradead.org> - 2017-05-21 09:10 +0200
Re: [PATCH 2/2] zram: do not count duplicated pages as compressed Minchan Kim <minchan@kernel.org> - 2017-05-21 09:20 +0200
csiph-web