Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2580997pxb; Fri, 5 Nov 2021 00:37:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwAq77Nfn8bSRLditmJuYVgE6niNFPtf/0fEh8lmjqvTTQYSycxil1k1GYi79byI3xFWty8 X-Received: by 2002:a05:6602:1487:: with SMTP id a7mr29760315iow.114.1636097841011; Fri, 05 Nov 2021 00:37:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1636097841; cv=none; d=google.com; s=arc-20160816; b=xbe3eCMU/qTeBMgXKQVFyXW8NYsHZ/ZOSXqUUWZJ0fbw0kj0a314oFKaFVVLeBjuvh 3nF0SvtEe9PFRVNwR2i/uzYq/sk6EPPRihhSIhpq2r5NDtDh6jVvMje7Ok3BSQw74mce +ojYbOjoy2nH0EVxQO2zDNztwTLPHkWKqGFSWj6SlT/Iq5DMxmulIEJI9ZZTv8L4j9I5 1OostxhwKSIHKehVAY++WJcD86M8PCrSxH/JBU/3431P8DI00J3WFSA3DCfVNG19WZTi OgCyV9cBMq4K8z8DVhw5IjEUUxOeAl+ACV0mWNSkp48B6vYLhze93kNmE8gnh7PyYpFH aTfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=471eGmUxaF67diQu9fpSiCy6uokW6qtVpUcaxV0sWLg=; b=j3hIPXhWQ9zNtVtyjujt8YwGrktn0fotWazKrHHbbGnX+0mIBnG72R3N7r09dI8WE0 OYqnr7afydtaPAhLzlyOmTjvA4H0yi6bgXo6QH5mXnoA0RxNls6IXV6FJaNvMziS/Ruu z8IHq0yuLcOa1qHmzmU+zb1XsWdTdHR3JsNBntR9HwekDnSNXmsshAKYJPgEM0Xb7KY3 Pn1alUdqx5jQipyDzziLz2QbDbmyvUvtdp+dNgHDMUeH0ipFH3FPLVBMerB5H8LEsqaG jR6UOhq27c9A1YiCuV13QW/SCqwFj+Zbi39VRQIQCcpisusqSdg5ix9qSgBX5K9NJSve Z6rA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=jS5yXBDc; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a13si9211214ilv.53.2021.11.05.00.37.07; Fri, 05 Nov 2021 00:37:20 -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; dkim=pass header.i=@gmail.com header.s=20210112 header.b=jS5yXBDc; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232068AbhKEGiP (ORCPT + 99 others); Fri, 5 Nov 2021 02:38:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229971AbhKEGiO (ORCPT ); Fri, 5 Nov 2021 02:38:14 -0400 Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2A966C061714; Thu, 4 Nov 2021 23:35:35 -0700 (PDT) Received: by mail-qk1-x72a.google.com with SMTP id bq14so7975951qkb.1; Thu, 04 Nov 2021 23:35:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=471eGmUxaF67diQu9fpSiCy6uokW6qtVpUcaxV0sWLg=; b=jS5yXBDc4yq8hyj2cMX5ZzypfkbcLj9UWr5FarIDV8R/zKENQbna+Jo8HNO42CtEMt RiopFHwHRn4GwPkE5mt3IdSzakYbUGSj2lbLs/YAsoK0ar9yVUh09Yhl8a4WWyQOjwZ+ ZMVvmuhWqz7vNgHbChGOHuDkC5/GG4HCHnSqsF5E+6MK0hng9T+RlaxODaBfqkN6w0KD OKWDtzvX8pHGd6kiigIdwo/20u19Uex8DStSUaqEFXYlC/NevQSYREnt+slq5II6jC87 rVCtpwgcKIuv2TtDWCxHgQLpa/HJ7hMsWJ5Fd6j9a8IyeYP3DdbyGWKU3ZTxpURg3r5p g1nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=471eGmUxaF67diQu9fpSiCy6uokW6qtVpUcaxV0sWLg=; b=3uKCzCu8VTWNV0wcXvreoSKjyaPUYwX+7g8ZHMmE4Gh/6bLk4yF67y7VrzFzDf4wGN CvuMUN6rJbCccamfauVszu6psGrsEpRrSZp4AxspfJV7HL5+ck6xGhI5IIXoWj7wV7oG ouDjI5GzkGQoTZ0RzA4zs3cYeDU5CH1NclNomSVGbeC5EVHzsntXvhZyUlyN51k2k/GZ ArraNeeCslddLWWjJhtNlBvs2VZQqc+ULoxPodOvRtE+r6ciYdl2qlfBIR858cFNVxVi D46ubnVZfsWUQGxzR4oj+GbsuLbBEDjII3dTjd6xSYUzXlhMa11WstLnrWwOVLMy6ZAc YiSA== X-Gm-Message-State: AOAM532MCZ0nymC6+h4cFbaYCBuLzuDAt5n/2FZqqSF7GNvWkQNaLeTw g1uE9gdYeLGqOa6CEDc5p4uqeEanBkuFZz1xNuw= X-Received: by 2002:a05:620a:408:: with SMTP id 8mr16641290qkp.116.1636094134305; Thu, 04 Nov 2021 23:35:34 -0700 (PDT) MIME-Version: 1.0 References: <20211101060419.4682-1-laoar.shao@gmail.com> In-Reply-To: From: Yafang Shao Date: Fri, 5 Nov 2021 14:34:58 +0800 Message-ID: Subject: Re: [PATCH v7 00/11] extend task comm from 16 to 24 To: =?UTF-8?B?TWljaGHFgiBNaXJvc8WCYXc=?= Cc: Andrew Morton , Kees Cook , Steven Rostedt , Mathieu Desnoyers , Arnaldo Carvalho de Melo , Petr Mladek , Peter Zijlstra , Al Viro , Valentin Schneider , Qiang Zhang , robdclark , christian , Dietmar Eggemann , Ingo Molnar , Juri Lelli , Vincent Guittot , David Miller , Jakub Kicinski , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin Lau , Song Liu , Yonghong Song , john fastabend , KP Singh , dennis.dalessandro@cornelisnetworks.com, mike.marciniszyn@cornelisnetworks.com, dledford@redhat.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org, netdev , bpf , "linux-perf-use." , linux-fsdevel@vger.kernel.org, Linux MM , LKML , kernel test robot , kbuild test robot Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 4, 2021 at 9:37 AM Micha=C5=82 Miros=C5=82aw wrote: > > On Mon, Nov 01, 2021 at 06:04:08AM +0000, Yafang Shao wrote: > > There're many truncated kthreads in the kernel, which may make trouble > > for the user, for example, the user can't get detailed device > > information from the task comm. > > > > This patchset tries to improve this problem fundamentally by extending > > the task comm size from 16 to 24, which is a very simple way. > [...] > > Hi, > > I've tried something like this a few years back. My attempt got mostly > lost in the mailing lists, but I'm still carrying the patches in my > tree [1]. My target was userspace thread names, and it turned out more > involved than I had time for. > > [1] https://rere.qmqm.pl/git/?p=3Dlinux;a=3Dcommit;h=3D2c3814268caf2b1fee= 6d1a0b61fd1730ce135d4a > and its parents > Hi Michal, Thanks for the information. I have looked through your patches. It seems to contain six patches now and can be divided into three parts per my understanding. 1. extend task comm len This parts contains below 4 patches: [prctl: prepare for bigger TASK_COMM_LEN](https://rere.qmqm.pl/git/?p=3Dlinux;a=3Dcommit;h=3Dcfd99db9c= f911bb4d106889aeba1dfe89b6527d0) [bluetooth: prepare for bigger TASK_COMM_LEN](https://rere.qmqm.pl/git/?p=3Dlinux;a=3Dcommit;h=3Dba2805f51= 96865b81cc6fc938ea53af2c7c2c892) [taskstats: prepare for bigger TASK_COMM_LEN](https://rere.qmqm.pl/git/?p=3Dlinux;a=3Dcommit;h=3D4d29bfedc= 57b36607915a0171f4864ec504908ca) [mm: make TASK_COMM_LEN configurable](https://rere.qmqm.pl/git/?p=3Dlinux;a=3Dcommit;h=3D362acc3558= 2445174589184c738c4d86ec7d174b) What kind of userspace issues makes you extend the task comm length ? Why not just use /proc/[pid]/cmdline ? 2. A fix Below patch: [procfs: signal /proc/PID/comm write truncation](https://rere.qmqm.pl/git/?p=3Dlinux;a=3Dcommit;h=3Dd72027388d4d= 95db5438a7a574e0a03ae4b5d6d7) It seems this patch is incomplete ? I don't know what it means to do. 3. A feature provided for pthread_getname_np Below patch: [procfs: lseek(/proc/PID/comm, 0, SEEK_END)](https://rere.qmqm.pl/git/?p=3Dlinux;a=3Dcommit;h=3D2c3814268caf2= b1fee6d1a0b61fd1730ce135d4a) It seems this patch is useful. With this patch the userspace can directly get the TASK_COMM_LEN through the API. --=20 Thanks Yafang