linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: chenqiwu <qiwuchen55@gmail.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: "qiwu.chen" <qiwuchen55@gmail.com>,
	corbet@lwn.net, catalin.marinas@arm.com, will@kernel.org,
	paulmck@kernel.org, akpm@linux-foundation.org,
	linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org
Subject: Re: [PATCH v4 1/2] panic: add option to dump task maps info in panic_print
Date: Wed, 25 Sep 2024 16:27:59 +0800	[thread overview]
Message-ID: <20240925082759.GB2941@rlk> (raw)
In-Reply-To: <20240924113322.GA7248@redhat.com>

On Tue, Sep 24, 2024 at 01:33:54PM +0200, Oleg Nesterov wrote:
> 
> You didn't move get_vma_name() from fs/proc/task_mmu.c, so it also depends
> on CONFIG_PROC_FS.
>
Sure, thanks for your advice. it should be moved to mm tree without CONFIG_PROC_FS
dependence.

> > +		if (path) {
> > +			name = d_path(path, name_buf, sizeof(name_buf));
> > +			name = IS_ERR(name) ? "?" : name;
> 
I think this is an easier way to get file path name which deals with IS_ERR(name) case.
> perhaps this needs mangle_path() ...
>

> > +		} else if (name || name_fmt) {
> > +			snprintf(name_buf, sizeof(name_buf), name_fmt ?: "%s", name);
> > +			name = name_buf;
> > +		}
> 
This refers to the code section of do_procmap_query().

> Why not
> 
> 		} else if (name_fmt) {
> 			snprintf(name_buf, sizeof(name_buf), name_fmt, name);
> 			name = name_buf;
> 		}
> ?
>
Sure, this is a better way to deal with name_fmt case.

> > +		if (name)
> > +			pr_info("%08lx-%08lx %c%c%c%c %08llx %s\n",
> > +				vma->vm_start, vma->vm_end,
> > +				flags & VM_READ ? 'r' : '-',
> > +				flags & VM_WRITE ? 'w' : '-',
> > +				flags & VM_EXEC ? 'x' : '-',
> > +				flags & VM_MAYSHARE ? 's' : 'p',
> > +				pgoff, name);
> 
> I don't really understand why you skip vma if !name...
> 
Well, the vma without name seems no sense for debugging, skipping it can reduce the
maps space. But the disadvantage is debuggers cannot get full maps of task,
perhaps we shouldn't skip it.

Thanks
Qiwu


  reply	other threads:[~2024-09-25  8:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24  7:43 qiwu.chen
2024-09-24  7:43 ` [PATCH v4 2/2] arm64: show signal info for global init qiwu.chen
2024-09-24 18:36   ` Oleg Nesterov
2024-09-25  3:54     ` chenqiwu
2024-09-25 12:05       ` Oleg Nesterov
2024-09-26 10:12         ` chenqiwu
2024-09-24 11:33 ` [PATCH v4 1/2] panic: add option to dump task maps info in panic_print Oleg Nesterov
2024-09-25  8:27   ` chenqiwu [this message]
2024-09-25 12:19     ` Oleg Nesterov
2024-09-26  3:30       ` chenqiwu
2024-09-24 15:06 ` kernel test robot
2024-09-24 15:06 ` kernel test robot
2024-10-01 11:23 ` Lorenzo Stoakes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240925082759.GB2941@rlk \
    --to=qiwuchen55@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=oleg@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox