linux-kernel - Re: [FYI] tux3: Core changes

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]

Date:	Wed, 20 May 2015 20:51:46 -0700 (PDT)
From:	David Lang <david@...g.hm>
To:	Daniel Phillips <daniel@...nq.net>
cc:	Rik van Riel <riel@...hat.com>, Jan Kara <jack@...e.cz>,
	linux-fsdevel@...r.kernel.org, tux3@...3.org,
	linux-kernel@...r.kernel.org,
	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
Subject: Re: [FYI] tux3: Core changes

On Wed, 20 May 2015, Daniel Phillips wrote:

> On 05/20/2015 03:51 PM, Daniel Phillips wrote:
>> On 05/20/2015 12:53 PM, Rik van Riel wrote:
>>> How does tux3 prevent a user of find_get_page() from reading from
>>> or writing into the pre-COW page, instead of the current page?
>>
>> Careful control of the dirty bits (we have two of them, one each
>> for front and back). That is what pagefork_for_blockdirty is about.
>
> Ah, and of course it does not matter if a reader is on the
> pre-cow page. It would be reading the earlier copy, which might
> no longer be the current copy, but it raced with the write so
> nobody should be surprised. That is a race even without page fork.

how do you prevent it from continuing to interact with the old version of the 
page and never see updates or have it's changes reflected on the current page?

David Lang
--
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/