linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Akemi Yagi <toracat@elrepo.org>
To: Waiman Long <longman@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	David Howells <dhowells@redhat.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: Performance regression introduced by commit b667b8673443 ("pipe: Advance tail pointer inside of wait spinlock in pipe_read()")
Date: Fri, 17 Jan 2020 13:30:20 -0800	[thread overview]
Message-ID: <CABA31DpOsnDxL8VcwRebU8RmAMqv9UAc5zRe8oz14f3-TeWSQA@mail.gmail.com> (raw)
In-Reply-To: <b70a0334-63be-b3a5-6f8a-714fbe4637c7@redhat.com>

On Fri, Jan 17, 2020 at 10:11 AM Waiman Long <longman@redhat.com> wrote:
>
> On 1/17/20 12:29 PM, Waiman Long wrote:
> > On 1/17/20 12:05 PM, Linus Torvalds wrote:

> >> GNU make v4.2.1 is buggy. The fix was done over two years ago, but
> >> there hasn't been a new release since then, so a lot of distributions
> >> have the buggy version..
> >>
> >> The fix is commit b552b05 ("[SV 51159] Use a non-blocking read with
> >> pselect to avoid hangs.") In the make the git tree.
> >>      Linus
> >
> > Yes, I did use make v4.2.1 which is the version that is shipped in
> > RHEL8. I will build new make and try it.

> > Longman
> >
> I built a make with the lastest make git tree and the problem was gone
> with the new make. So it was a bug in make not the kernel. Sorry for the
> noise.
>
> Longman

If you are using RHEL8, building your own make is the only solution at
this time. There is a bugzilla entry filed for this make bug but the
progress is slow:

https://bugzilla.redhat.com/show_bug.cgi?id=1774790

The same bug in Fedora make was dealt with fairly quickly, thanks to
the great "pressure" from Linus. ;-)

Akemi

      parent reply	other threads:[~2020-01-17 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 16:53 Performance regression introduced by commit b667b8673443 ("pipe: Advance tail pointer inside of wait spinlock in pipe_read()") Waiman Long
     [not found] ` <CAHk-=wink2z6EtvhKfhSvfC2hKBseVU8UWsM+HLsQP9x3mD7Xw@mail.gmail.com>
     [not found]   ` <5c184396-7cc8-ee72-2335-dce9a977c8d4@redhat.com>
2020-01-17 18:11     ` Waiman Long
2020-01-17 19:20       ` Linus Torvalds
2020-01-17 21:30       ` Akemi Yagi [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=CABA31DpOsnDxL8VcwRebU8RmAMqv9UAc5zRe8oz14f3-TeWSQA@mail.gmail.com \
    --to=toracat@elrepo.org \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).