lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Tue, 22 Dec 2020 02:07:53 +0000
From:   "Song Bao Hua (Barry Song)" <>
To:     Vitaly Wool <>
CC:     Shakeel Butt <>,
        Minchan Kim <>,
        "Mike Galbraith" <>,
        LKML <>,
        linux-mm <>,
        Sebastian Andrzej Siewior <>,
        NitinGupta <>,
        Sergey Senozhatsky <>,
        Andrew Morton <>,
        "tiantao (H)" <>
Subject: RE: [PATCH] zsmalloc: do not use bit_spin_lock

> I'm still not convinced. Will kmap what, src? At this point src might become just a bogus pointer. 

As long as the memory is still there, we can kmap it by its page struct. But if
it is not there anymore, we have no way.

> Why couldn't the object have been moved somewhere else (due to the compaction mechanism for instance)
> at the time DMA kicks in?

So zs_map_object() will guarantee the src won't be moved by holding those preemption-disabled lock?
If so, it seems we have to drop the MOVABLE gfp in zswap for zsmalloc case?

> >
> > ~Vitaly


Powered by blists - more mailing lists