From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754547AbbJNQk0 (ORCPT ); Wed, 14 Oct 2015 12:40:26 -0400 Received: from mail-lf0-f52.google.com ([209.85.215.52]:36475 "EHLO mail-lf0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752776AbbJNQkZ (ORCPT ); Wed, 14 Oct 2015 12:40:25 -0400 Date: Wed, 14 Oct 2015 19:40:21 +0300 From: Cyrill Gorcunov To: Andy Lutomirski , Stas Sergeev Cc: x86@kernel.org, linux-kernel@vger.kernel.org, Brian Gerst , Denys Vlasenko , Linus Torvalds , Borislav Petkov , Pavel Emelyanov Subject: Re: [RFC 3/4] x86/signal/64: Re-add support for SS in the 64-bit signal context Message-ID: <20151014164021.GS2048@uranus> References: <6e14e2f7ce1c38fc1996bd4d5d3d9dc70b8bd94d.1444697927.git.luto@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6e14e2f7ce1c38fc1996bd4d5d3d9dc70b8bd94d.1444697927.git.luto@kernel.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 12, 2015 at 06:04:07PM -0700, Andy Lutomirski wrote: ... > > For the benefit of new 64-bit software that uses segmentation (new > versions of DOSEMU might), the new behavior can be detected with a > new ucontext flag UC_SIGCONTEXT_SS. > > To avoid compilation issues, __pad0 is left as an alias for ss in > ucontext. > > The nitty-gritty details are documented in the header file. > > Cc: Stas Sergeev > Cc: Linus Torvalds > Cc: Cyrill Gorcunov > Cc: Pavel Emelyanov > Signed-off-by: Andy Lutomirski Andy, so for old criu versions (prior the 1.5.1 which is Mar 2015, in next versions we already write proper ss into the images) we've been providing __pad = 0, which is ss in a new meaning, and the kernel will overwrite it with @user-ds after this series, correct? This should work for us. Stas, mind to refresh my memory, which ss value doesmu setups here?