linux-kernel - RE: Questin about swap_slot free and invalidate page

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: <7793705b-a076-4c5a-be4d-9572d7560860@default>
Date:	Thu, 21 Feb 2013 13:42:21 -0800 (PST)
From:	Dan Magenheimer <dan.magenheimer@...cle.com>
To:	Ric Mason <ric.masonn@...il.com>
Cc:	Minchan Kim <minchan@...nel.org>, Hugh Dickins <hughd@...gle.com>,
	Nitin Gupta <ngupta@...are.org>,
	Seth Jennings <sjenning@...ux.vnet.ibm.com>,
	Konrad Rzeszutek Wilk <konrad@...nok.org>,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: RE: Questin about swap_slot free and invalidate page

> From: Ric Mason [mailto:ric.masonn@...il.com]
> Subject: Re: Questin about swap_slot free and invalidate page
> 
> On 02/19/2013 11:27 PM, Dan Magenheimer wrote:
> >> From: Ric Mason [mailto:ric.masonn@...il.com]
> >>> Hugh is right that handling the possibility of duplicates is
> >>> part of the tmem ABI.  If there is any possibility of duplicates,
> >>> the ABI defines how a backend must handle them to avoid data
> >>> coherency issues.
> >>>
> >>> The kernel implements an in-kernel API which implements the tmem
> >>> ABI.  If the frontend and backend can always agree that duplicate
> >> Which ABI in zcache implement that?
> > https://oss.oracle.com/projects/tmem/dist/documentation/api/tmemspec-v001.pdf
> >
> > The in-kernel APIs are frontswap and cleancache.  For more information about
> > tmem, see http://lwn.net/Articles/454795/
> 
> But you mentioned that you have in-kernel API which can handle
> duplicate.  Do you mean zcache_cleancache/frontswap_put_page? I think
> they just overwrite instead of optional flush the page on the
> second(duplicate) put as mentioned in your tmemspec.

Maybe I am misunderstanding your question...  The spec allows
overwrite (and return success) OR flush the page (and return
failure).  Zcache does the latter (flush).  The code that implements
it is in tmem_put.

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