From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964877AbaFQQT7 (ORCPT ); Tue, 17 Jun 2014 12:19:59 -0400 Received: from mail-ve0-f181.google.com ([209.85.128.181]:56606 "EHLO mail-ve0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933321AbaFQQT4 convert rfc822-to-8bit (ORCPT ); Tue, 17 Jun 2014 12:19:56 -0400 MIME-Version: 1.0 In-Reply-To: <53A060F7.2020304@gmx.de> References: <539F1C59.6070308@gmx.de> <539F297F.7010904@nod.at> <539F2B2D.6050105@gmx.de> <539F3077.7040005@gmx.de> <539F35A0.2050002@gmx.de> <539F567F.2050802@gmx.de> <539F5702.5050104@nod.at> <53A060F7.2020304@gmx.de> From: Andy Lutomirski Date: Tue, 17 Jun 2014 09:19:33 -0700 Message-ID: Subject: Re: 3.15: kernel BUG at kernel/auditsc.c:1525! To: =?UTF-8?Q?Toralf_F=C3=B6rster?= Cc: Richard Weinberger , "H. Peter Anvin" , X86 ML , Eric Paris , Linux Kernel Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 17, 2014 at 8:38 AM, Toralf Förster wrote: > On 06/16/2014 11:35 PM, Andy Lutomirski wrote: >> [cc: hpa, x86 list] >> >> On Mon, Jun 16, 2014 at 1:43 PM, Richard Weinberger wrote: >>> Am 16.06.2014 22:41, schrieb Toralf Förster: >>>> Well, might be the mail:subject should be adapted, b/c the issue can be triggered in a 3.13.11 kernel too. >>>> Unfortunately it does not appear within an UML guest, therefore an automated bisecting isn't possible I fear. >>> >>> You could try KVM. :) >> >> Before you do that, just to clarify: >> >> What bitness is your kernel? That is, are you on 32-bit or 64-bit kernel? >> >> What bitness is your test case? 'file a.out' will say. >> >> What does /proc/cpuinfo say in flags? >> > > tfoerste@n22 ~/tmp $ uname -a > Linux n22 3.15.1 #4 SMP Tue Jun 17 17:22:22 CEST 2014 i686 Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz GenuineIntel GNU/Linux So entry_32.S is in play. > flags : ... sep ... And sysenter is in use, barring weird boot-time options. > > >> Can you try the attached patch? It's only compile-tested. >> > applied both on top of 3.14.8 and 3.15.1 - issue solved So I guess I diagnosed it right. Yay for reading ugly code. hpa, should I resend a real emailed patch or is my attached thing ok? Presumably this, or something like it, should cc: stable and go in 3.16, too. --Andy