From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Date: Tue, 06 Jun 2017 09:40:12 +0000 Subject: Re: kernel of next-20170602 call trace when run add_key02 in LTP Message-Id: <25659.1496742012@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit List-Id: References: <20170605172855.GA87699@gmail.com> <20170605134823.GA24454@rei.lan> In-Reply-To: <20170605172855.GA87699@gmail.com> To: Eric Biggers Cc: dhowells@redhat.com, Cyril Hrubis , Bixuan Cui , linux-kernel@vger.kernel.org, James Morris , "Serge E. Hallyn" , keyrings@vger.kernel.org, ltp@lists.linux.it Eric Biggers wrote: > David, can you get keys-next up to date with keys-fixes so that people > don't run into this bug? Note that it was also hit with the Trinity fuzzer. Done. David From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751435AbdFFJkR (ORCPT ); Tue, 6 Jun 2017 05:40:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47504 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751394AbdFFJkQ (ORCPT ); Tue, 6 Jun 2017 05:40:16 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 197D88123D Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=dhowells@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 197D88123D Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20170605172855.GA87699@gmail.com> References: <20170605172855.GA87699@gmail.com> <20170605134823.GA24454@rei.lan> To: Eric Biggers Cc: dhowells@redhat.com, Cyril Hrubis , Bixuan Cui , linux-kernel@vger.kernel.org, James Morris , "Serge E. Hallyn" , keyrings@vger.kernel.org, ltp@lists.linux.it Subject: Re: kernel of next-20170602 call trace when run add_key02 in LTP MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25658.1496742012.1@warthog.procyon.org.uk> Date: Tue, 06 Jun 2017 10:40:12 +0100 Message-ID: <25659.1496742012@warthog.procyon.org.uk> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Tue, 06 Jun 2017 09:40:15 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Eric Biggers wrote: > David, can you get keys-next up to date with keys-fixes so that people > don't run into this bug? Note that it was also hit with the Trinity fuzzer. Done. David From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Date: Tue, 06 Jun 2017 10:40:12 +0100 Subject: [LTP] kernel of next-20170602 call trace when run add_key02 in LTP In-Reply-To: <20170605172855.GA87699@gmail.com> References: <20170605172855.GA87699@gmail.com> <20170605134823.GA24454@rei.lan> Message-ID: <25659.1496742012@warthog.procyon.org.uk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it Eric Biggers wrote: > David, can you get keys-next up to date with keys-fixes so that people > don't run into this bug? Note that it was also hit with the Trinity fuzzer. Done. David