linux-kernel - Re: 2.6.19-rc2-mm1

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:	Fri, 20 Oct 2006 04:10:18 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Carsten Otte <cotte@...enet.de>
CC:	Andrew Morton <akpm@...l.org>, Cedric Le Goater <clg@...ibm.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Gabriel C <nix.or.die@...glemail.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.19-rc2-mm1

Carsten Otte wrote:
> Andrew Morton wrote:
> 
>> The page we're writing into isn't locked, so there's no deadlock afaict.
>>
>> But then, I forget how xip works.  Carsten, is it actually being used for
>> anything?
>>   
> 
> The comment may be superfluous. I did not quite understand the deadlock 
> condition refered to by the comment in filemap, therefore I cut&pasted 
> it over. I will send a patch that removes it.

Yes, it wasn't a good comment. Basically we can't hold the page lock and
then enter the page fault handler. mm-fix-pagecache-write-deadlocks.patch
has quite a lot of comments to explain it.

I don't believe filemap_xip holds the page lock, so you don't need to do
the atomic copy, and you don't need to do the fault_in_pages_readable.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 
-
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/