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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 1 Oct 2021 16:22:04 -0700
From:   Andrew Morton <>
To:     Brian Geffon <>
Cc:     Minchan Kim <>, Nitin Gupta <>,
        Sergey Senozhatsky <>,
        Jonathan Corbet <>,,,,
        Suleiman Souhlal <>,
        Jesse Barnes <>
Subject: Re: [PATCH] zram: Allow backing device to be assigned after init

On Fri,  1 Oct 2021 11:16:27 -0700 Brian Geffon <> wrote:

> There does not appear to be a technical reason to not
> allow the zram backing device to be assigned after the
> zram device is initialized.
> This change will allow for the backing device to be assigned
> as long as no backing device is already assigned. In that
> event backing_dev would return -EEXIST.

Why is this useful?

Powered by blists - more mailing lists