From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Jason@zx2c4.com Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id a8334dab for ; Sun, 6 Nov 2016 12:21:14 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id c099e833 for ; Sun, 6 Nov 2016 12:21:13 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 06201888 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Sun, 6 Nov 2016 12:21:12 +0000 (UTC) Received: by mail-lf0-f46.google.com with SMTP id t196so94662703lff.3 for ; Sun, 06 Nov 2016 04:22:48 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <1289478110.20161106110707@vodka.home.kg> References: <25241985.20161106100258@vodka.home.kg> <1289478110.20161106110707@vodka.home.kg> From: "Jason A. Donenfeld" Date: Sun, 6 Nov 2016 13:22:46 +0100 Message-ID: To: k@vodka.home.kg Content-Type: text/plain; charset=UTF-8 Cc: WireGuard mailing list Subject: Re: [WireGuard] mips32 crash List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, Nov 6, 2016 at 9:07 AM, wrote: >> <4>[13905.634933] Process (pid: 41189632, threadinfo=82bca000, task=810000ce, tls=8100cea5) > >> Likely caused by memory corruption. > > Look at pid value. Its defenitly not valid pid. Task structure was > corrupted. Indeed. In hex, the bottom part is 0x8100, which is an address...