Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753436AbcCYPsl (ORCPT ); Fri, 25 Mar 2016 11:48:41 -0400 Received: from arcturus.aphlor.org ([188.246.204.175]:46550 "EHLO arcturus.aphlor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752769AbcCYPsk (ORCPT ); Fri, 25 Mar 2016 11:48:40 -0400 Date: Fri, 25 Mar 2016 11:48:35 -0400 From: Dave Jones To: luto@kernel.org Cc: x86@kernel.org, Linux Kernel Subject: x32 processes, with CONFIG_X86_X32 not set Message-ID: <20160325154835.GA13116@codemonkey.org.uk> Mail-Followup-To: Dave Jones , luto@kernel.org, x86@kernel.org, Linux Kernel MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Score: -2.9 (--) X-Spam-Report: Spam detection software, running on the system "arcturus.aphlor.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: I had a trinity process get stuck last overnight. The reason for it getting stuck is my bug (I think), but there's an odd unrelated thing I noticed while debugging this.. $ strace -p 20966 strace: Process 20966 attached strace: [ Process PID=20966 runs in x32 mode. ] [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 452 Lines: 15 I had a trinity process get stuck last overnight. The reason for it getting stuck is my bug (I think), but there's an odd unrelated thing I noticed while debugging this.. $ strace -p 20966 strace: Process 20966 attached strace: [ Process PID=20966 runs in x32 mode. ] So I don't use that new-fangled x32 stuff. I don't even have CONFIG_X86_X32 compiled in. Is this strace getting confused, or did we somehow screw up the syscall entry code ? Dave