Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp1635929ybk; Thu, 21 May 2020 11:28:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzpHoGmD3AxnUWMUonUlpiKBNuZFhL706AH3DbFC81LZgOLkeAl84r5zh5w8SMRkfx3pHrq X-Received: by 2002:a17:906:94c6:: with SMTP id d6mr4994745ejy.88.1590085695825; Thu, 21 May 2020 11:28:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590085695; cv=none; d=google.com; s=arc-20160816; b=rJqh8DgQM2O/KEUfNiRJMgH5vODnNH1Y0m8jUkf+6vlVJCEyzAYG1ARObW+/1L+XUc T5ufFAVNbCr1UpfWmBbcIHH44ZjtCCeumPFwpVaJiOPnSdda/wdNSAraf9/+Ht8mmOsg e/J4csSxzTY4zHsvWF7zS2fvRF2mDUtOOZ2kYmN16SWVKDDN0/uouauRUj8EY77K8wM4 L0Mz11o9WsjIcRSlDWoTNMPZjRR0QdMPuMDR/KwKkH7FMRDaPZ58SJN+GXxWqkBfUA0b 9OUJ4epNJj/wk7dGeQN5qgMXQsQDN1UCeJ0FyQ8uJ5OCk8/5FN+tRDbkF05FTIfGc15S RY+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=mQLYpDIb7e5h8PrtSXgOqT3It1cJwpvGClX78yP2dIA=; b=hYdQ/X9SNl9Ju3hIgE4WAF5Im6bkBPMmdByOEMHbcV6+rE1x9fMD7jeiLSKpuGCIT2 aCJNqZdtteHHHEgDAK0wuK5yOgKcYv962xb3gIdDEd+Hk30MahmJ4xCDG93acUJySf+s LqfWbDoj4sL0JayImmidLN+SBW9pnqCt4XoqX5jJN/mlj+vGeHPm7Y3VXAR4UUV53LzI IWFo+EoGHWvx4DxuoHBYYHlyjSwdfncd6R5z315CrucAF+Ngr439PZuW2r2Gv/0lrqo/ hqlXhxIqKbJqgEfI9NapvALnoi4iST9hU3ET5ns1ZvlgByZZ5X9aFIhohJn4lxkC7f49 OzqQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ly17si3530112ejb.148.2020.05.21.11.27.43; Thu, 21 May 2020 11:28:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-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-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728670AbgEUS06 (ORCPT + 99 others); Thu, 21 May 2020 14:26:58 -0400 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:45649 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728240AbgEUS06 (ORCPT ); Thu, 21 May 2020 14:26:58 -0400 Received: from callcc.thunk.org (pool-100-0-195-244.bstnma.fios.verizon.net [100.0.195.244]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 04LIQocA007023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 May 2020 14:26:50 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id 2CF13420304; Thu, 21 May 2020 14:26:50 -0400 (EDT) Date: Thu, 21 May 2020 14:26:50 -0400 From: "Theodore Y. Ts'o" To: Ritesh Harjani Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, Jan Kara , "Aneesh Kumar K . V" Subject: Re: [RFC 16/16] ext4: Add process name and pid in ext4_msg() Message-ID: <20200521182650.GC2946569@mit.edu> References: <3d99e1291b3bc8f2a78467d11b1a7a31393180fc.1589086800.git.riteshh@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3d99e1291b3bc8f2a78467d11b1a7a31393180fc.1589086800.git.riteshh@linux.ibm.com> Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Sun, May 10, 2020 at 11:54:56AM +0530, Ritesh Harjani wrote: > This adds process name and pid for ext4_msg(). > I found this to be useful. For e.g. below print gives more > info about process name and pid. > > [ 7671.131912] [mount/12543] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: acl,user_xattr I'm not entirely sure about adding the command/pid at the beginning of the message. The way we do this in ext4_warning and ext4_err is to print that information like this: printk(KERN_CRIT "EXT4-fs error (device %s): %s:%d: comm %s: %pV\n", sb->s_id, function, line, current->comm, &vaf); ... and I wonder if it would make more sense to add something like to ext4_msg(), just out of consistency's sake. Which of the debugging messages were you finding this to be most helpful? - Ted