From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 21C8DC77B73 for ; Tue, 2 May 2023 13:52:59 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id B929C6B0074; Tue, 2 May 2023 09:52:58 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B42F56B0075; Tue, 2 May 2023 09:52:58 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A322D6B0078; Tue, 2 May 2023 09:52:58 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) by kanga.kvack.org (Postfix) with ESMTP id 8AA896B0074 for ; Tue, 2 May 2023 09:52:58 -0400 (EDT) Received: by mail-qt1-f180.google.com with SMTP id d75a77b69052e-3ef36d814a5so152271cf.0 for ; Tue, 02 May 2023 06:52:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1683035578; x=1685627578; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=uUoPyEclplnbQ5nsG5OgNwVF48A7g0Micb2U/fMXHNA=; b=WwkoPfhPIxlaRvGzyZGForsAUMlHfQvpw3m6ELc4mNRMCx9anH8knbZM8fnRh9Zout ug95p8dQqh4gMNoO3hW18eCqTptU17S/rU3QeuwNOaO1GkeXlIxWqE/zm9U/aN65EahT as7LeV16C2A2tV8alP4xL0I8moDM/9qO8GqG+klcLKONOJu+6EiADWQRBqWp8c3tO2Z9 VRaFHZzWNAqT7o/gYlg5b8vU0ibb1tkrHtHBPGbQCw3LBsQeLuPV6hUtAjUc0Bbg/hSK mTBlAsXTvQIazHXvRMvrYqNIQRONDUL2e4dvjXojaHfCJl2W21V1L+OBK9zCD2DNZrzc NUDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683035578; x=1685627578; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=uUoPyEclplnbQ5nsG5OgNwVF48A7g0Micb2U/fMXHNA=; b=LdrfMJW5UG65+qg0DhSARoKCP/Wv0Rsh21PTcYZBB+oDyDWWbBp0DGe6zaQ/CvfqXi BWinkTTBzen55yFfA/Sn4ELcFLs8VPP3H7CPb1KDd7OUnzZcXzrJ3fKoPD90gZVDJwU8 HK6QVhq6EPVOK7EN4QWDMf9PuDamIL8oo8+4n8NIl1HkE7pQCFHeokfpVHEUHxI44Mpe /aDx2Q5JZZJXyDtcO64KibtVyYh6zv7Dyx47P2Qsvy/sSE8rDZKCLuM5ZVvvHC+mam9f 0elyuernBTaLoJtMZrPksU6R8lK4561wDwm1ngNYSaf3p3MOlVICyYlrDxh6sowf/gCO SI/Q== X-Gm-Message-State: AC+VfDx4hzGnJBpAB9bnQrQ3u8iUGBs8LlCuRVeF4xDVElPKC+q59i3h hmjYv9bLRD/Ax0CupQ8kwQw4UB4wE1+AFUZ1XriPR8GJuI7tAjFeHlwdiXPa X-Google-Smtp-Source: ACHHUZ5CuqN0ueoP6LXfs8ZQiH2iNDJ0f/JbMmFWBRGoqTLO5Al7z/X8HDiTurSelO2YjDTLfuq7qw0/Vdw1XZ8K+mA= X-Received: by 2002:ac8:7f47:0:b0:3ef:62f2:52df with SMTP id g7-20020ac87f47000000b003ef62f252dfmr21723qtk.9.1682978568636; Mon, 01 May 2023 15:02:48 -0700 (PDT) MIME-Version: 1.0 References: <20230215143306.2d563215@rorschach.local.home> In-Reply-To: From: Peter Collingbourne Date: Mon, 1 May 2023 15:02:37 -0700 Message-ID: Subject: Re: [PATCH v3 1/3] kasan: switch kunit tests to console tracepoints To: Steven Rostedt Cc: Marco Elver , andrey.konovalov@linux.dev, Andrew Morton , Andrey Konovalov , Alexander Potapenko , Dmitry Vyukov , Andrey Ryabinin , kasan-dev@googlegroups.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrey Konovalov , Masami Hiramatsu , linux-trace-kernel@vger.kernel.org, Nick Desaulniers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000262, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, Feb 23, 2023 at 10:45=E2=80=AFPM Peter Collingbourne wrote: > > On Wed, Feb 15, 2023 at 11:33 AM Steven Rostedt wro= te: > > > > On Wed, 15 Feb 2023 09:57:40 +0100 > > Marco Elver wrote: > > > > > Yes, you are right, and it's something I've wondered how to do better > > > as well. Let's try to consult tracing maintainers on what the right > > > approach is. > > > > I have to go and revisit the config options for CONFIG_FTRACE and > > CONFIG_TRACING, as they were added when this all started (back in > > 2008), and the naming was rather all misnomers back then. > > > > "ftrace" is really for just the function tracing, but CONFIG_FTRACE > > really should just be for the function tracing infrastructure, and > > perhaps not even include trace events :-/ But at the time it was > > created, it was for all the "tracers" (this was added before trace > > events). > > It would be great to see this cleaned up. I found this aspect of how > tracing works rather confusing. > > So do you think it makes sense for the KASAN tests to "select TRACING" > for now if the code depends on the trace event infrastructure? Any thoughts? It looks like someone else got tripped up by this: https://reviews.llvm.org/D144057 Peter