linux-kernel - Re: Re : vm: weird behaviour when munmapping

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0611201213460.11655@blonde.wat.veritas.com>
Date:	Mon, 20 Nov 2006 12:20:03 +0000 (GMT)
From:	Hugh Dickins <hugh@...itas.com>
To:	Francis Moreau <francis.moro@...il.com>
cc:	a.p.zijlstra@...llo.nl, linux-kernel@...r.kernel.org
Subject: Re: Re : vm: weird behaviour when munmapping

On Mon, 20 Nov 2006, Francis Moreau wrote:
> 
> I end up to see "open(B), close(B)" sequence when unmapping a part of
> the dumb device that I found strange. I think that "open(A') close(B)"
> can give more information to the driver and reflect that B is unmapped
> and A' is still mapped and becomes the new mapped area.
> But it's may be just me...

I think I do now get your point.  But your way round doesn't really
reflect what's going on either: the range A' was already open and now
you open it again.  Until there's some driver actually needing more
sophisticated treatment, let's just leave it the simple way it is.

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