linux-kernel - Re: mlock: Make the mlock system call interruptible by fatal

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] [day] [month] [year] [list]

Message-Id: <20080924092040.d8407311.akpm@linux-foundation.org>
Date:	Wed, 24 Sep 2008 09:20:40 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	sqazi@...gle.com (Salman Qazi), linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: mlock: Make the mlock system call interruptible by fatal

On Wed, 24 Sep 2008 11:22:55 +0100 Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

> > > Can we do
> > >
> > >        return i ? i : -EINTR;
> > >
> > > in the usual fashion?
> > 
> > Fixed.
> 
> If its only interruptible by fatal signals why do we care what the return
> is ?
> 

For the immediate in-kernel caller.  __get_user_pages() took a ref on a
few pages which the caller needs to undo before doing anything else
(like processing the signal).

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