Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Song Liu <songliubraving@fb.com>
To:     Vince Weaver <vincent.weaver@maine.edu>
CC:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "Peter Zijlstra" <peterz@infradead.org>,
        "mingo@kernel.org" <mingo@kernel.org>
Subject: Re: perf: fuzzer leads to trace_kprobe: Could not insert message
 flood
Thread-Topic: perf: fuzzer leads to trace_kprobe: Could not insert message
 flood
Thread-Index: AQHT0NsKF6lgcxb36UeZZJCEysMOEaP6arGA
Date:   Tue, 10 Apr 2018 19:57:50 +0000
Message-ID: <A3B3905F-3364-462A-BE02-B01D52482791@fb.com>
References: <alpine.DEB.2.21.1804101043490.6068@macbook-air>
In-Reply-To: <alpine.DEB.2.21.1804101043490.6068@macbook-air>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: fb.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A339817453B4AD45A5871491263FE1B6@namprd15.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: cef312a2-4033-455f-f7cb-08d59f1d5741
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Apr 2018 19:57:50.8977
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR15MB1756
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-04-10_08:,,
 signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


> On Apr 10, 2018, at 7:48 AM, Vince Weaver <vincent.weaver@maine.edu> wrot=
e:
>=20
> Author: Song Liu <songliubraving@fb.com>
> Date:   Wed Dec 6 14:45:15 2017 -0800
>=20
> When running the perf_fuzzer on a current git checkout my logs are floode=
d=20
> with messages such as this:
> [71487.869077] trace_kprobe: Could not insert probe at unknown+0: -22
> [71488.174479] trace_kprobe: Could not insert probe at unknown+0: -22
>=20
> Presumably this is due to the introduction of the perf_kprobe PMU in
> 	commit e12f03d7031a977356e3d7b75a68c2185ff8d155
> 	Author: Song Liu <songliubraving@fb.com>
> 	Date:   Wed Dec 6 14:45:15 2017 -0800
>=20
> Is there a way to get this error disabled, or else rate-limited?
>=20
> Vince

Hi Vince,=20

Thanks for the report.=20

This is a new API that creates probe together with perf_event_open(). Based=
 on=20
my limited understanding of perf_fuzzer, it doesn't understand this API, an=
d uses=20
it in an abnormal way. I would recommend perf_fuzzer to understand this new
API and test it. For more information about using this API, please refer to=
 the=20
man-page diff available at:

      https://patchwork.kernel.org/patch/10097283/

Thanks again for the test and report. Please let me know if you have furthe=
r=20
questions.=20

Best,=20
Song=