From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934107AbdCUTgj (ORCPT ); Tue, 21 Mar 2017 15:36:39 -0400 Received: from mail-lf0-f47.google.com ([209.85.215.47]:35491 "EHLO mail-lf0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755420AbdCUTfD (ORCPT ); Tue, 21 Mar 2017 15:35:03 -0400 Date: Tue, 21 Mar 2017 22:34:59 +0300 From: Cyrill Gorcunov To: Andy Lutomirski Cc: Dmitry Safonov , "linux-kernel@vger.kernel.org" , Dmitry Safonov <0x7f454c46@gmail.com>, Adam Borowski , "linux-mm@kvack.org" , Andrei Vagin , Borislav Petkov , "Kirill A. Shutemov" , X86 ML , "H. Peter Anvin" , Andy Lutomirski , Ingo Molnar , Thomas Gleixner Subject: Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Message-ID: <20170321193459.GG21564@uranus.lan> References: <20170321163712.20334-1-dsafonov@virtuozzo.com> <20170321171723.GB21564@uranus.lan> <6648805c-e0d8-5e27-9e19-602ab47937a7@virtuozzo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 21, 2017 at 12:31:51PM -0700, Andy Lutomirski wrote: ... > > I guess the question comes from that we're releasing CRIU 3.0 with > > 32-bit C/R and some other cool stuff, but we don't support x32 yet. > > As we don't want release a thing that we aren't properly testing. > > So for a while we should error on dumping x32 applications. > > I'm curious: shouldn't x32 CRIU just work? What goes wrong? Anything ;) We didn't tried as far as I know but i bet somthing will be broken for sure. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f72.google.com (mail-lf0-f72.google.com [209.85.215.72]) by kanga.kvack.org (Postfix) with ESMTP id BB13A6B03A6 for ; Tue, 21 Mar 2017 15:35:02 -0400 (EDT) Received: by mail-lf0-f72.google.com with SMTP id g70so92358784lfh.4 for ; Tue, 21 Mar 2017 12:35:02 -0700 (PDT) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com. [2a00:1450:4010:c07::235]) by mx.google.com with ESMTPS id g141si11857283lfg.86.2017.03.21.12.35.01 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Mar 2017 12:35:01 -0700 (PDT) Received: by mail-lf0-x235.google.com with SMTP id a6so70963953lfa.0 for ; Tue, 21 Mar 2017 12:35:01 -0700 (PDT) Date: Tue, 21 Mar 2017 22:34:59 +0300 From: Cyrill Gorcunov Subject: Re: [PATCHv2] x86/mm: set x32 syscall bit in SET_PERSONALITY() Message-ID: <20170321193459.GG21564@uranus.lan> References: <20170321163712.20334-1-dsafonov@virtuozzo.com> <20170321171723.GB21564@uranus.lan> <6648805c-e0d8-5e27-9e19-602ab47937a7@virtuozzo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Andy Lutomirski Cc: Dmitry Safonov , "linux-kernel@vger.kernel.org" , Dmitry Safonov <0x7f454c46@gmail.com>, Adam Borowski , "linux-mm@kvack.org" , Andrei Vagin , Borislav Petkov , "Kirill A. Shutemov" , X86 ML , "H. Peter Anvin" , Andy Lutomirski , Ingo Molnar , Thomas Gleixner On Tue, Mar 21, 2017 at 12:31:51PM -0700, Andy Lutomirski wrote: ... > > I guess the question comes from that we're releasing CRIU 3.0 with > > 32-bit C/R and some other cool stuff, but we don't support x32 yet. > > As we don't want release a thing that we aren't properly testing. > > So for a while we should error on dumping x32 applications. > > I'm curious: shouldn't x32 CRIU just work? What goes wrong? Anything ;) We didn't tried as far as I know but i bet somthing will be broken for sure. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org