linux-kernel - Re: [PATCH v6 RESEND 0/2] vfs: have syncfs() return error when there are writeback errors

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: <20200428164819.7b58666b755d2156aa46c56c@linux-foundation.org>
Date:   Tue, 28 Apr 2020 16:48:19 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Jeff Layton <jlayton@...nel.org>
Cc:     viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
        andres@...razel.de, willy@...radead.org, dhowells@...hat.com,
        hch@...radead.org, jack@...e.cz, david@...morbit.com
Subject: Re: [PATCH v6 RESEND 0/2] vfs: have syncfs() return error when
 there are writeback errors

On Tue, 28 Apr 2020 09:51:53 -0400 Jeff Layton <jlayton@...nel.org> wrote:

> Just a resend since this hasn't been picked up yet. No real changes
> from the last set (other than adding Jan's Reviewed-bys). Latest
> cover letter follows:

I see no cover letter here.

> 
> --------------------------8<----------------------------
> 
> v6:
> - use READ_ONCE to ensure that compiler doesn't optimize away local var
> 
> The only difference from v5 is the change to use READ_ONCE to fetch the
> bd_super pointer, to ensure that the compiler doesn't refetch it
> afterward. Many thanks to Jan K. for the explanation!
> 
> Jeff Layton (2):
>   vfs: track per-sb writeback errors and report them to syncfs
>   buffer: record blockdev write errors in super_block that it backs

http://lkml.kernel.org/r/20200207170423.377931-1-jlayton@kernel.org

has suitable-looking words, but is it up to date?