linux-kernel - Re: [PATCH] vmscan: add barrier to prevent evictable page in unevictable list

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: <20110928180503.GC1696@barrios-desktop>
Date:	Thu, 29 Sep 2011 03:05:03 +0900
From:	Minchan Kim <minchan.kim@...il.com>
To:	Lin Ming <mlin@...pku.edu.cn>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-mm <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Johannes Weiner <jweiner@...hat.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Mel Gorman <mel@....ul.ie>, Rik van Riel <riel@...hat.com>,
	Lee Schermerhorn <lee.schermerhorn@...com>
Subject: Re: [PATCH] vmscan: add barrier to prevent evictable page in
 unevictable list

On Wed, Sep 28, 2011 at 11:04:05PM +0800, Lin Ming wrote:
> On Wed, Sep 28, 2011 at 9:45 AM, Minchan Kim <minchan.kim@...il.com> wrote:
> > When racing between putback_lru_page and shmem_unlock happens,
> 
> s/shmem_unlock/shmem_lock/

I did it intentionally for represent shmem_lock with user = 1, lock = 0.
If you think it makes others confusing, I will change in next version.
Thanks.

> 
> > progrom execution order is as follows, but clear_bit in processor #1
> > could be reordered right before spin_unlock of processor #1.
> > Then, the page would be stranded on the unevictable list.

-- 
Kind regards,
Minchan Kim
--
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/