From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 84AB4C77B7F for ; Thu, 11 May 2023 09:36:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237613AbjEKJgu (ORCPT ); Thu, 11 May 2023 05:36:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56774 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237718AbjEKJgg (ORCPT ); Thu, 11 May 2023 05:36:36 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7C95D8A4E for ; Thu, 11 May 2023 02:36:33 -0700 (PDT) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1683797792; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0MlX4bO/xsxPE0sSg+a9U+jP9cGlaqB1yl1v5aiA+/E=; b=TTbWyGieMlEBBfbnkkY2EjapO14NeDqkq0x0sOHxK+4SkaEf9CTwaLgxc37OSO/YGqdnL4 NdqPIWtt3FzESBpZZZi3JSVyEdOmqep77spuecl+uzVA62tKAzK3WZn/MKql+w/1H41ilH 9axz1e4Pz8rhXM1DVP/coKZgThf6AT2m73CBHYD6PN/1iFOj5DxCm8aH1hJ4j98Yr4RNNV jTIzypG7lXD8Gxmf+buhXmD5sZFL51nkoVCL+5/3PvXqrHU5lJO2PWk/GWzyQmIuadvKHL QP/+KtnOlfmxt/VPks9SrKZEW77RGT9I53tUXGM2AXDrwNlyLDOKJ1NYklganQ== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1683797792; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=0MlX4bO/xsxPE0sSg+a9U+jP9cGlaqB1yl1v5aiA+/E=; b=2hBMTzm/9BDA3Z81b8FkbaaU1N6TgJ2274PVQdsEibctklbW7+IwuVAriE+8iE2S51Co7A vkqTM4imuSxSBSCA== To: Pavel Tikhomirov , Andrey Vagin Cc: Frederic Weisbecker , LKML , Anna-Maria Behnsen , Peter Zijlstra , syzbot+5c54bd3eb218bb595aa9@syzkaller.appspotmail.com, Dmitry Vyukov , Sebastian Siewior , Michael Kerrisk , Christian Brauner , Alexander Mikhalitsyn , Pavel Emelyanov Subject: Re: [RFD] posix-timers: CRIU woes In-Reply-To: References: <20230425181827.219128101@linutronix.de> <20230425183312.932345089@linutronix.de> <87zg6i2xn3.ffs@tglx> <87v8h62vwp.ffs@tglx> <878rdy32ri.ffs@tglx> <87v8h126p2.ffs@tglx> <875y911xeg.ffs@tglx> <87ednpyyeo.ffs@tglx> Date: Thu, 11 May 2023 11:36:31 +0200 Message-ID: <87r0rnciqo.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 11 2023 at 11:17, Pavel Tikhomirov wrote: > On 10.05.2023 16:16, Andrey Vagin wrote: >>> >>> So because of that half thought out user space ABI we are now up the >>> regression creek without a paddle, unless CRIU can accomodate to a >>> different restore mechanism to lift this restriction from the kernel. >>> >> If you give us a new API to create timers with specified id-s, we will >> figure out how to live with it. It isn't good to ask users to update >> CRIU to work on new kernels, but here are reasons and event improvements >> for CRIU, so I think it's worth it. > > I agree, any API to create timers with specified id-s would work for new > CRIU versions. The real question is whether this will cause any upheaval when a new kernel meets a non-updated CRIU stack. You know the UABI regression rules of the kernel... Thanks, tglx