linux-kernel - Re: [patch 2/5] mm: fault vs invalidate/truncate race fix

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: <Pine.LNX.4.64.0610110916540.3952@g5.osdl.org>
Date:	Wed, 11 Oct 2006 09:21:16 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Andrew Morton <akpm@...l.org>
cc:	Nick Piggin <nickpiggin@...oo.com.au>,
	Nick Piggin <npiggin@...e.de>,
	Linux Memory Management <linux-mm@...ck.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch 2/5] mm: fault vs invalidate/truncate race fix

On Tue, 10 Oct 2006, Andrew Morton wrote:
>
> On Wed, 11 Oct 2006 15:39:22 +1000
> Nick Piggin <nickpiggin@...oo.com.au> wrote:
> 
> > But I see that it does read twice. Do you want that behaviour retained? It
> > seems like at this level it would be logical to read it once and let lower
> > layers take care of any retries?
> 
> argh.  Linus has good-sounding reasons for retrying the pagefault-path's
> read a single time, but I forget what they are.  Something to do with
> networked filesystems?  (adds cc)

Indeed. We _have_ to re-try a failed IO that we didn't start ourselves.

The original IO could have been started by a person who didn't have 
permissions to actually carry it out successfully, so if you enter with 
the page locked (because somebody else started the IO), and you wait for 
the page and it's not up-to-date afterwards, you absolutely _have_ to try 
the IO, and can only return a real IO error after your _own_ IO has 
failed.

There is another issue too: even if the page was marked as having an error 
when we entered (and no longer locked - maybe the IO failed last time 
around), we should _still_ re-try. It might be a temporary error that has 
since gone away, and if we don't re-try, we can end up in the totally 
untenable situation where the kernel makes a soft error into a hard one. 

Neither case simply isn't acceptable. End result: only things like 
read-ahead should actually honor the "page exists but is not up-to-date" 
as a "don't even try".

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/