public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Baokun Li <libaokun1@huawei.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	oliver.sang@intel.com, beibei.si@intel.com, jannh@google.com,
	mszeredi@redhat.com, torvalds@linux-foundation.org,
	yukuai3@huawei.com
Subject: Re: [PATCH 5.4] fget: clarify and improve __fget_files() implementation
Date: Mon, 28 Feb 2022 12:08:58 +0100	[thread overview]
Message-ID: <YhytSkOJ7caNbTDj@kroah.com> (raw)
In-Reply-To: <20220226063201.167183-1-libaokun1@huawei.com>

On Sat, Feb 26, 2022 at 02:32:01PM +0800, Baokun Li wrote:
> From: Linus Torvalds <torvalds@linux-foundation.org>
> 
> commit e386dfc56f837da66d00a078e5314bc8382fab83 upstream.
> 
> Commit 054aa8d439b9 ("fget: check that the fd still exists after getting
> a ref to it") fixed a race with getting a reference to a file just as it
> was being closed.  It was a fairly minimal patch, and I didn't think
> re-checking the file pointer lookup would be a measurable overhead,
> since it was all right there and cached.
> 
> But I was wrong, as pointed out by the kernel test robot.
> 
> The 'poll2' case of the will-it-scale.per_thread_ops benchmark regressed
> quite noticeably.  Admittedly it seems to be a very artificial test:
> doing "poll()" system calls on regular files in a very tight loop in
> multiple threads.
> 
> That means that basically all the time is spent just looking up file
> descriptors without ever doing anything useful with them (not that doing
> 'poll()' on a regular file is useful to begin with).  And as a result it
> shows the extra "re-check fd" cost as a sore thumb.
> 
> Happily, the regression is fixable by just writing the code to loook up
> the fd to be better and clearer.  There's still a cost to verify the
> file pointer, but now it's basically in the noise even for that
> benchmark that does nothing else - and the code is more understandable
> and has better comments too.
> 
> [ Side note: this patch is also a classic case of one that looks very
>   messy with the default greedy Myers diff - it's much more legible with
>   either the patience of histogram diff algorithm ]
> 
> Link: https://lore.kernel.org/lkml/20211210053743.GA36420@xsang-OptiPlex-9020/
> Link: https://lore.kernel.org/lkml/20211213083154.GA20853@linux.intel.com/
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Tested-by: Carel Si <beibei.si@intel.com>
> Cc: Jann Horn <jannh@google.com>
> Cc: Miklos Szeredi <mszeredi@redhat.com>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
> ---
>  fs/file.c | 73 +++++++++++++++++++++++++++++++++++++++++++------------
>  1 file changed, 57 insertions(+), 16 deletions(-)

All now queued up, thanks for the backports!

greg k-h

      reply	other threads:[~2022-02-28 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26  6:32 [PATCH 5.4] fget: clarify and improve __fget_files() implementation Baokun Li
2022-02-28 11:08 ` Greg KH [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=YhytSkOJ7caNbTDj@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=beibei.si@intel.com \
    --cc=jannh@google.com \
    --cc=libaokun1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=oliver.sang@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yukuai3@huawei.com \
    /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