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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 35B66C433FE for ; Tue, 21 Dec 2021 11:58:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237346AbhLUL6e (ORCPT ); Tue, 21 Dec 2021 06:58:34 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:34933 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230184AbhLUL6c (ORCPT ); Tue, 21 Dec 2021 06:58:32 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1640087911; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7lYrU1K2CMwMBqu1I8UYlhY98XiUZOOoKEZAWN+V6pw=; b=GbEyQJYS2hIb9W5ZRwYFhNll9Ahlg20Afby6poz++ZYVXFAV3g+T7Deus3Ae+xmicSC+TF EPNSLmjMxAsw2IB8H6vhs61C8ZsXOHXKo6DL11xWQvOJpeafpEDyUL2JUl+cM2Ym9m0csg /36r9J4ZHeU+48TPnFCEiiUXrdXe+SI= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-532-uLETqQXvNIaTLMkn98tDcQ-1; Tue, 21 Dec 2021 06:58:30 -0500 X-MC-Unique: uLETqQXvNIaTLMkn98tDcQ-1 Received: by mail-wm1-f72.google.com with SMTP id ay40-20020a05600c1e2800b003458b72e865so1345884wmb.9 for ; Tue, 21 Dec 2021 03:58:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=7lYrU1K2CMwMBqu1I8UYlhY98XiUZOOoKEZAWN+V6pw=; b=wD7n6lBLtHGLMIq176Yb6Mu24jSEzPrWspvAe1gpaJbjQtGZCjazLQoYzD6TRhlebT zWkepEE2l7/NOh4rieO9gjIbJdXULXXPR+yQKzSv4Wlo8NJGycYSV8QMowwD7NG8w+Ga qfHYSQG/MhIWLT2ij7hCHAN9WYVteyinDRKrOnqs1zY8XqGGyUtgjew/Ld0r1tVGZJ56 FJsvfehmxNCSdg6+QSFfNT47+hicoh8yU4zSH9vysrqWHge46ctHm0gb13Fvai4CJ4V2 HIWVZAK2mAjQ+47iwaktWEfMsYXrAItwXb17Ir5dPP3IHj6U4PklBrHmPsfOVKFGuisL sanQ== X-Gm-Message-State: AOAM530wYed58vufkbnbX9pLgp84alHkwI3fX11jCJM4hXtaxK6m07e3 ZURuRF0Hiebfe+k/Cmq5gu8DoHxEI/OWUkcb2kP8LP2WnLzRDQkbp7DWyk5kaDpS+TvOepB7azA GRj+vHNZjL9ueUQYI/PHQxRU= X-Received: by 2002:a1c:721a:: with SMTP id n26mr2367341wmc.39.1640087909480; Tue, 21 Dec 2021 03:58:29 -0800 (PST) X-Google-Smtp-Source: ABdhPJyxO75Z3tWfiJRwbhR1Ae2esgoCvkNBWJYDgw7Gh8Rm+9+pyY5hVxVf8ZXo8JIjLxfTbvGX4A== X-Received: by 2002:a1c:721a:: with SMTP id n26mr2367328wmc.39.1640087909340; Tue, 21 Dec 2021 03:58:29 -0800 (PST) Received: from localhost (cpc111743-lutn13-2-0-cust979.9-3.cable.virginm.net. [82.17.115.212]) by smtp.gmail.com with ESMTPSA id s1sm10035421wrr.8.2021.12.21.03.58.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 21 Dec 2021 03:58:28 -0800 (PST) Date: Tue, 21 Dec 2021 11:58:28 +0000 From: Aaron Tomlin To: Petr Mladek Cc: Luis Chamberlain , Christoph Lameter , Miroslav Benes , Andrew Morton , jeyu@kernel.org, linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org, atomlin@atomlin.com, ghalat@redhat.com Subject: Re: [RFC PATCH] module: Introduce module unload taint tracking Message-ID: <20211221115828.cnuazprjdgfpebag@ava.usersys.com> X-PGP-Key: http://pgp.mit.edu/pks/lookup?search=atomlin%40redhat.com X-PGP-Fingerprint: 7906 84EB FA8A 9638 8D1E 6E9B E2DE 9658 19CC 77D6 References: <20211124173327.3878177-1-atomlin@redhat.com> <20211209153131.a54fdfbci4qnyy6h@ava.usersys.com> <20211210160931.ftvxpulno73a2l7c@ava.usersys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 2021-12-13 16:16 +0100, Petr Mladek wrote: > > I'm not so sure about this. We could gather such details already via Ftrace > > (e.g. see load_module()). Personally, I'd prefer to maintain a simple list. > > Fair enough. It was just an idea. Simple list is a good start. We > could always add more details if people find it useful. Indeed we could. > Also we should keep in mind that the default panic() message should > be reasonably short. Only the last lines might be visible on screen. > Serial consoles might be really slow. Absolutely, I agree. This feature should be entirely optional. In fact, it is likely only useful while reviewing the data via /proc/vmcore given the potential amount of data generated, in addition to that seen in panic_print_sys_info(), when explicitly enabled. Kind regards, -- Aaron Tomlin