linux-kernel - Re: POSIX violation by writeback error

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: <20180904210237.GA12303@bombadil.infradead.org>
Date:   Tue, 4 Sep 2018 14:02:37 -0700
From:   Matthew Wilcox <willy@...radead.org>
To:     Vito Caputo <vcaputo@...garu.com>
Cc:     Jeff Layton <jlayton@...hat.com>,
        "J. Bruce Fields" <bfields@...ldses.org>,
        Rogier Wolff <R.E.Wolff@...Wizard.nl>,
        焦晓冬 <milestonejxd@...il.com>,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: POSIX violation by writeback error

On Tue, Sep 04, 2018 at 01:35:34PM -0700, Vito Caputo wrote:
> Implement a new class of swap space for backing dirty pages which fail
> to write back.  Pages in this space survive reboots, essentially backing
> the implicit commitment POSIX establishes in the face of asynchronous
> writeback errors.  Rather than evicting these pages as clean, they are
> swapped out to the persistent swap.

You not only need to track which index within a file this swapped page
belongs to but also which file.  And that starts to get tricky.  It may
or may not have a name; it may or may not have a persistent inode number;
it may or may not have a persistent fhandle.  If it's on network storage,
it may have been modified by another machine.  If it's on removable
storage, it may have been modified by another machine.