linux-kernel - Re: [RFC PATCH v2 9/9] s390/s390x: allocate sys

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: <20150917133930.06c3b26b@mschwide>
Date:	Thu, 17 Sep 2015 13:39:30 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc:	heiko carstens <heiko.carstens@...ibm.com>,
	linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-api <linux-api@...r.kernel.org>
Subject: Re: [RFC PATCH v2 9/9] s390/s390x: allocate sys_membarrier system
 call number

On Wed, 16 Sep 2015 15:20:05 +0000 (UTC)
Mathieu Desnoyers <mathieu.desnoyers@...icios.com> wrote:

> ----- On Sep 7, 2015, at 12:15 PM, Mathieu Desnoyers mathieu.desnoyers@...icios.com wrote:
> 
> > [ Untested on this architecture. To try it out: fetch linux-next/akpm,
> >  apply this patch, build/run a membarrier-enabled kernel, and do make
> >  kselftest. ]
> 
> Hi,
> 
> sys_membarrier has been merged into Linux 4.3-rc1. It can therefore
> be tested on top of Linus' master by applying this patch.

Successfully tested with todays Linus' master, membarrier_test has passed.
Patch applied to linux-s390 but with a different system call number.
#355 is already taken by sys_userfaultfd, the new one for membarrier is #356.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

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