On (24/12/12 17:55), caiqingfu wrote: > > I see that somebody posted something similar on the bugzilla [1]. Is > > that person you, by any chance? If so, can you please post your > > findings to linux kernel mailing list? E.g. linux-ext4@, Cc-ing > > linux-fsdevevl@ and linux-mm@ would be a good start. Bugzilla is > > not used. > > > > If this problem is in ext4 then I'd really prefer to address it there and > > drop this patch from zram, simply because it covers an issue in the upper > > layer. And it's better to fix issues that to cover them. > > > > [1] https://bugzilla.kernel.org/show_bug.cgi?id=219548 > > He is my colleague, he reported a bug Oh, I see. > In any case, zram should ensure that its data is not damaged zram cannot ensure that, it's not zram's job. Nothing stops the buggy actor from modifiying the page at any random point, zram might not even be able to decompress the page in the end, it's not only the zs_handle allocation slow-path case.
