Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp613800pxb; Thu, 15 Apr 2021 02:21:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyI3XVWLVXkdEaOqqZeX5hMCScYr167oBkSGLe9+RrIJhaw2n0QQ7Xcm5GcOFY/VKG9koG+ X-Received: by 2002:a50:eb45:: with SMTP id z5mr2983301edp.243.1618478507462; Thu, 15 Apr 2021 02:21:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618478507; cv=none; d=google.com; s=arc-20160816; b=Dyb+H5TKkmx+wjqj9+YpFX1QzvgJ0673ohJ6jsFO7yj8n7DRUkFTJaX9qh2K3wAiml sLtNL4u4Y018M/0Coz+dJyI+NMPh9wreUHKP/MJr0ntTxYyNlBLiybAoZOeX/EQcr2vE 7YQJuGT6KuT0uxuXSdPpzjXQgqs4onGUAdvW2yGpED5VlsFvvOlo9fL++kA6WtV0JwIw KNXf/Gn2Tpo5O8BlE5FeyIeII2aLadkV1QMlqhScDENjrVySdmV3GJwT5nHG4vraT3F3 Guva/xc3cWtRNhC9OnWuwhes3/Ty6dGFmLC0LkGvtKNZeQI4klU9WmOYuGGCWXMnICrU 3mrQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:ironport-sdr:ironport-sdr; bh=brYXv/5/0+PMz+01hDoQptDxMzBymYIo07YjWjatF/E=; b=Pg08YXblsJtJzAwK2g2Wscy8LabjvnkHJKMhf5f1s8M39ansrjhrX3ytZxNkTZHJKb B74GJFIq37ZOQIpXBfHBLDArMJXXYaf1dJfzq+98NOImtrqDazpTy62ZC6g7KcBKfGbo G9JPjTAsElmBHXjOL3W4ZQagoxyPJcKkRR80uRfO/a3liDRvwYdJrafKA+UPi2fx9iXE xi7hEMOMhC1A1wPhhfUNzScJeEmoRv9VguMMI99EAEQLm9nPukv8AYiz4sh5pU2HpYRV 5se1ZAapwWrqMbU48lq3dZlLgRyguT0OKutoETT9Tpi3NZwd42aOUngsAhleWa1Um9xB i/RA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m9si1879050edq.499.2021.04.15.02.21.16; Thu, 15 Apr 2021 02:21:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231500AbhDOJUm (ORCPT + 99 others); Thu, 15 Apr 2021 05:20:42 -0400 Received: from mga14.intel.com ([192.55.52.115]:26136 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231388AbhDOJUk (ORCPT ); Thu, 15 Apr 2021 05:20:40 -0400 IronPort-SDR: 9Z0vg8P6gX/DCdgLdbCPrQocmlP1+Kq94A9vtj/INKPfkbrUXSPo25jSpnmBJnUumDZ7KcgH0S MwSBhua5+0EA== X-IronPort-AV: E=McAfee;i="6200,9189,9954"; a="194383848" X-IronPort-AV: E=Sophos;i="5.82,223,1613462400"; d="scan'208";a="194383848" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Apr 2021 02:20:16 -0700 IronPort-SDR: n5soXkagFEqGqwFmH8J/fHl9ftelwXXgyTGTn83FZG4lrlItyzBPeIkqVI2EgtgMjNXvlKQ1IP 04g8avGPvBOw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.82,223,1613462400"; d="scan'208";a="444123430" Received: from um.fi.intel.com (HELO um) ([10.237.72.62]) by fmsmga004.fm.intel.com with ESMTP; 15 Apr 2021 02:20:14 -0700 From: Alexander Shishkin To: Greg Kroah-Hartman Cc: Andy Shevchenko , linux-kernel@vger.kernel.org, alexander.shishkin@linux.intel.com Subject: Re: [PATCH 2/7] stm class: Replace uuid_t with plain u8 uuid[16] In-Reply-To: References: <20210414171251.14672-1-alexander.shishkin@linux.intel.com> <20210414171251.14672-3-alexander.shishkin@linux.intel.com> <87sg3sfzl1.fsf@ashishki-desk.ger.corp.intel.com> Date: Thu, 15 Apr 2021 12:20:14 +0300 Message-ID: <87pmyvgb01.fsf@ashishki-desk.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Greg Kroah-Hartman writes: > On Wed, Apr 14, 2021 at 10:14:34PM +0300, Alexander Shishkin wrote: >> Greg Kroah-Hartman writes: >> >> >> Using raw buffer APIs against uuid_t / guid_t. >> > >> > So you want to do that, or you do not want to do that? Totally >> > confused, >> >> My understanding is that: >> 1) generate_random_uuid() use is allegedly bad even though it's in their >> header, >> 2) poking directly at the byte array inside uuid_t is bad, even though, >> again, header. >> >> It is, indeed, not ideal. >> >> If agreeable, I'll update this patch to the below and respin the whole >> series. > > You are showing that Andy wrote this, when you are the one that did :( That's intentional, it's Andy's patch. In fact, it was probably me who insisted on the open-coded-byte-array version, in an offline conversation some time ago. I'd like to keep his name on it if that's ok. I've re-sent it [1] as a standalone patch. > Anyway, I've dropped this single patch from the series and applied the > rest. Feel free to send this patch as a stand-alone one once you have > the authorship issues sorted out. Thank you! [1] https://lore.kernel.org/lkml/20210415091555.88085-1-alexander.shishkin@linux.intel.com/ Regards, -- Alex