From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Zeev Tarantov <zeev.tarantov@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: commit 1cb41fe7e34a43a1d27dfdb6d65699786dd44c20 in stable (v3.3.3) breaks perf
Date: Mon, 23 Apr 2012 09:25:48 -0700 [thread overview]
Message-ID: <20120423162547.GA27669@kroah.com> (raw)
In-Reply-To: <20120423063704.GA3465@myhost>
On Mon, Apr 23, 2012 at 09:37:04AM +0300, Zeev Tarantov wrote:
> gcc correctly complains:
>
> util/hist.c: In function ‘__hists__add_entry’:
> util/hist.c:240:27: error: invalid type argument of ‘->’ (have ‘struct hist_entry’)
> util/hist.c:241:23: error: invalid type argument of ‘->’ (have ‘struct hist_entry’)
>
> for this new code:
>
> + if (he->ms.map != entry->ms.map) {
> + he->ms.map = entry->ms.map;
> + if (he->ms.map)
> + he->ms.map->referenced = true;
> + }
>
> because "entry" is a "struct hist_entry", not a pointer to a struct.
>
> In mainline, "entry" is a pointer to struct passed as argument to the function.
> So this is broken during backporting. But obviously not compile tested.
> Greg wrote on G+ that those who did not test 3.3.3-rc1 have no right to complain, but I'm complaining anyway. :P
>
> See trivial patch to fix this.
> -Z.T.
>
> P.S.
> I don't need credit for the patch so it's ok if my diff doesn't apply because of messed up whitespace.
> Just fix it.
Patch looks good to me, thanks for doing this, you are right in that I
didn't test perf. I'll go queue this up right now.
greg k-h
next prev parent reply other threads:[~2012-04-23 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 6:37 commit 1cb41fe7e34a43a1d27dfdb6d65699786dd44c20 in stable (v3.3.3) breaks perf Zeev Tarantov
2012-04-23 16:25 ` Greg Kroah-Hartman [this message]
2012-04-23 16:29 ` Patch "Perf: fix build breakage" has been added to the 3.0-stable tree gregkh
2012-04-23 16:29 ` Patch "Perf: fix build breakage" has been added to the 3.3-stable tree gregkh
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=20120423162547.GA27669@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zeev.tarantov@gmail.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