mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <rong.a.chen@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>, lkp@lists.01.org
Subject: Re: [non] 2aa3847085: will-it-scale.per_process_ops -32.0% regression
Date: Mon, 6 Apr 2020 16:39:30 +0800	[thread overview]
Message-ID: <20200406083930.GV8179@shao2-debian> (raw)
In-Reply-To: <20200406020451.GQ23230@ZenIV.linux.org.uk>

On Mon, Apr 06, 2020 at 03:04:51AM +0100, Al Viro wrote:
> On Mon, Apr 06, 2020 at 09:25:39AM +0800, kernel test robot wrote:
> > Greeting,
> > 
> > FYI, we noticed a -32.0% regression of will-it-scale.per_process_ops due to commit:
> > 
> > 
> > commit: 2aa38470853a65dc9b1b4bd0989d34cd3fc57ebd ("non-RCU analogue of the previous commit")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> 
> Arrgghh...  Could you check if vfs.git#fixes recovers that?  FWIW, proposed fix
> is this:
> 
> commit d98d78cd6ac9eb5ed0506140cc43432d7c7dd480
> Author: Al Viro <viro@zeniv.linux.org.uk>
> Date:   Sun Apr 5 21:59:55 2020 -0400
> 
>     fix braino in legitimize_path()
>     
>     brown paperbag time... wrong order of arguments ended up confusing
>     the values to check dentry and mount_lock seqcounts against.
>     
>     Reported-by: kernel test robot <rong.a.chen@intel.com>
>     Fixes: 2aa38470853a ("non-RCU analogue of the previous commit")
>     Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> 
> diff --git a/fs/namei.c b/fs/namei.c
> index 61fdb77a7d58..a320371899cf 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -610,7 +610,7 @@ static bool __legitimize_path(struct path *path, unsigned seq, unsigned mseq)
>  static inline bool legitimize_path(struct nameidata *nd,
>  			    struct path *path, unsigned seq)
>  {
> -	return __legitimize_path(path, nd->m_seq, seq);
> +	return __legitimize_path(path, seq, nd->m_seq);
>  }
>  
>  static bool legitimize_links(struct nameidata *nd)


Hi Al,

Yes, the regression can be fixed:

7ef482fa65513b18  2aa38470853a65dc9b1b4bd098  d98d78cd6ac9eb5ed0506140cc  testcase/testparams/testbox
----------------  --------------------------  --------------------------  ---------------------------
         %stddev      change         %stddev      change         %stddev
             \          |                \          |                \  
    449960             -32%     306036                      450924        will-it-scale/performance-open2-ucode=0x21/lkp-ivb-d04
    449959             -32%     306035                      450923        GEO-MEAN will-it-scale.per_process_ops

Best Regards,
Rong Chen

      reply	other threads:[~2020-04-06  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06  1:25 kernel test robot
2020-04-06  2:04 ` Al Viro
2020-04-06  8:39   ` kernel test robot [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=20200406083930.GV8179@shao2-debian \
    --to=rong.a.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@lists.01.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®