linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: willy@infradead.org, andriy.shevchenko@linux.intel.com,
	david@redhat.com, linmiaohe@huawei.com, vbabka@suse.cz,
	cl@linux.com, penberg@kernel.org, rientjes@google.com,
	iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
	rostedt@goodmis.org, sergey.senozhatsky@gmail.com,
	joe@perches.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, lkp@intel.com
Subject: Re: [PATCH v6 resend 0/3] mm, vsprintf: dump full information of page flags in pGp
Date: Fri, 19 Mar 2021 17:05:21 +0100	[thread overview]
Message-ID: <YFTLwdP8sETTNTiY@alley> (raw)
In-Reply-To: <20210319101246.73513-1-laoar.shao@gmail.com>

On Fri 2021-03-19 18:12:43, Yafang Shao wrote:
> The existed pGp shows the names of page flags only, rather than the full
> information including section, node, zone, last cpuipid and kasan tag.
> While it is not easy to parse these information manually because there
> are so many flavors. We'd better interpret them in printf.
> 
> This patchset also includes some code cleanup in mm/slub.c.
> 
> v6:
> - fixes the build failure and test failure reported by kernel test robot
> 
> 
> Yafang Shao (3):
>   mm, slub: use pGp to print page flags
>   mm, slub: don't combine pr_err with INFO
>   vsprintf: dump full information of page flags in pGp
> 
>  Documentation/core-api/printk-formats.rst |  2 +-
>  lib/test_printf.c                         | 90 ++++++++++++++++++++---
>  lib/vsprintf.c                            | 66 +++++++++++++++--
>  mm/slub.c                                 | 13 ++--
>  4 files changed, 149 insertions(+), 22 deletions(-)

The patchset has been pushed into printk/linux.git, branch
for-5.13-vsprintf-pgp. It should appear in linux-next again.

The first two patches are the same as in v5 that has already been
pushed earlier. I probably should have replaced only the last patch
but I rebased everything. It was too easy with the b4 tool. And
it is Friday late afternoon here.

Best Regards,
Petr

      parent reply	other threads:[~2021-03-19 16:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 10:12 [PATCH v6 resend 0/3] mm, vsprintf: dump full information of page flags in pGp Yafang Shao
2021-03-19 10:12 ` [PATCH v6 resend 1/3] mm, slub: use pGp to print page flags Yafang Shao
2021-03-19 10:12 ` [PATCH v6 resend 2/3] mm, slub: don't combine pr_err with INFO Yafang Shao
2021-03-19 10:12 ` [PATCH v6 resend 3/3] vsprintf: dump full information of page flags in pGp Yafang Shao
2021-03-19 15:27   ` Petr Mladek
2021-03-19 10:15 ` [PATCH v6 resend 0/3] mm, " Yafang Shao
2021-03-19 12:22   ` Petr Mladek
2021-03-19 15:03 ` Sergey Senozhatsky
2021-03-19 16:05 ` Petr Mladek [this message]

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=YFTLwdP8sETTNTiY@alley \
    --to=pmladek@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=cl@linux.com \
    --cc=david@redhat.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=joe@perches.com \
    --cc=laoar.shao@gmail.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).