linux-kernel - Re: [PATCH v3 3/3] zram: support BDI_CAP_STABLE

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <20161127130104.GA4919@tigerII>
Date:   Sun, 27 Nov 2016 22:01:04 +0900
From:   Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:     Minchan Kim <minchan@...nel.org>
Cc:     Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, Takashi Iwai <tiwai@...e.de>,
        Hyeoncheol Lee <cheol.lee@....com>, yjay.kim@....com,
        Sangseok Lee <sangseok.lee@....com>,
        Hugh Dickins <hughd@...gle.com>, stable@...r.kernel.org
Subject: Re: [PATCH v3 3/3] zram: support BDI_CAP_STABLE_WRITES

On (11/26/16 23:41), Minchan Kim wrote:
[..]
> > >  	mutex_lock(&bdev->bd_mutex);
> > 
> > why not set it just once, when we allocate queue/disk and configure both
> > of them:  in zram_add()
> 
> I should have mentioned the reason.
> The revalidate_disk reset the BDI_CAP_STABLE_WRITES.

aha. either sets or clears it in blk_integrity_revalidate(),
now I see it.

	-ss