On (25/01/30 13:42), Sergey Senozhatsky wrote: > This is Part II of the series [1] that makes zram read() and write() > preemptible. This part focuses only zsmalloc because zsmalloc imposes > atomicity restrictions on its users. One notable example is object > mapping API, which returns with: > a) local CPU lock held > b) zspage rwlock held I'll combine this series and zram series [1] and send out as one patch set. [1] https://lore.kernel.org/linux-mm/20250130111105.2861324-1-senozhatsky@xxxxxxxxxxxx
