From: Doug Ledford <dledford@redhat.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Gunthorpe, Jason" <jgg@ziepe.ca>
Subject: Re: [GIT PULL] Please pull rdma.git
Date: Mon, 29 Apr 2019 14:17:35 -0400 [thread overview]
Message-ID: <acf2b9a82e0c28a9c63d04a8153e1ff4fc814327.camel@redhat.com> (raw)
In-Reply-To: <20190429180055.GX6705@mtr-leonro.mtl.com>
[-- Attachment #1: Type: text/plain, Size: 1829 bytes --]
On Mon, 2019-04-29 at 21:00 +0300, Leon Romanovsky wrote:
> On Mon, Apr 29, 2019 at 01:13:01PM -0400, Doug Ledford wrote:
> > On Mon, 2019-04-29 at 09:48 -0700, Linus Torvalds wrote:
> > > On Mon, Apr 29, 2019 at 9:29 AM Doug Ledford <dledford@redhat.com> wrote:
> > > > drivers/infiniband/core/uverbs_main.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > This trivial one-liner is actually incorrect.
> > >
> > > It should use 'vmf->address', because the point of the ZERO_PAGE
> > > argument is to pick the page with the right virtual address alias for
> > > broken architectures that need those kinds.
> > >
> > > I'm actually surprised s390 wants it, usually it's just MIPS that has
> > > the horribly broken virtual address translation stuff. But it looks
> > > like for s390 it's at least only a performance issue (ie it causes
> > > some aliases in L1 that cause cacheline ping-pong rather than anything
> > > else).
> >
> > That's what I get for listening to Jason ;-)
> >
> > Well, since you have just essentially re-written the patch to be
> > correct, you are now the developer of origin. Do you want to commit the
> > fix directly or shall I respin it for you to pull?
>
> Linus already committed it.
>
> The whole breakage is mystery for me, the patch which introduced
> breakage, got successful build report from 0-build.
Yeah, successful 0-day build is a good indicator, but not a guarantee.
You just can't test all possible permutations and sometimes things slip
by. But it's still way better than 20 years ago when half the patches
weren't even compile tested before coming to Linus ;-)
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-04-29 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 16:28 [GIT PULL] Please pull rdma.git Doug Ledford
2019-04-29 16:48 ` Linus Torvalds
2019-04-29 17:13 ` Doug Ledford
2019-04-29 18:00 ` Leon Romanovsky
2019-04-29 18:17 ` Doug Ledford [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=acf2b9a82e0c28a9c63d04a8153e1ff4fc814327.camel@redhat.com \
--to=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=torvalds@linux-foundation.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