From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6346E72 for ; Thu, 23 Sep 2021 13:13:57 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id 0E34A61164; Thu, 23 Sep 2021 13:13:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1632402836; bh=b7ciuEU81I/+7+Kcf5GtQcPnxHNd6AApdTsqk+hICIc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=b6dQij5uc96X0dTcnPcoUuxkPTLbF2fN2/4Y5WaYYhXJ6M2KOCv5+18SPDtUxEOMv JhsZevCeAarVQfrdBBLKmDTCCmizljQrOD2L/1iNv8E+2eF4KifI/fsdwvO+G0uLoF PgeaGsco1S9SgPDGj0lg6aesyAuewN/oXBER2PLk= Date: Thu, 23 Sep 2021 15:13:53 +0200 From: Greg KH To: Guo Zhi Cc: nsaenz@kernel.org, peterz@infradead.org, maz@kernel.org, bsegall@google.com, rdunlap@infradead.org, airlied@redhat.com, kan liang , odin@uged.al, bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-staging@lists.linux.dev, linux-kernel Subject: Re: [PATCH] staging: vchip_arm: Fix misuse of %x Message-ID: References: <20210923035554.669434-1-qtxuning1999@sjtu.edu.cn> <590112814.393656.1632401860257.JavaMail.zimbra@sjtu.edu.cn> Precedence: bulk X-Mailing-List: linux-staging@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <590112814.393656.1632401860257.JavaMail.zimbra@sjtu.edu.cn> A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Thu, Sep 23, 2021 at 08:57:40PM +0800, Guo Zhi wrote: > We should restrict kernel pointer leakage issue by using kptr_restrict. > Therefore kernel pointers should be specified by %pK rather than %lx. I totally agree. What I am asking about is why is this message needed at all? Why not just remove the whole thing? Who uses it? thanks, greg k-h 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 X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A8A6CC433EF for ; Thu, 23 Sep 2021 13:16:06 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6550B611B0 for ; Thu, 23 Sep 2021 13:16:06 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 6550B611B0 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=mWlfbNMWPznoo/iEEn2il7fIFv5OUd+o2HI+Qrjcys4=; b=w+cYOPx3vwtPON gDEOa0QJLAM0yIURHHhAGvONWNkwlfweDv1gvyoV8fESopEsOOBITK4oZv42VEnPWxpew2zXr+KUv 84TJ+iKE9ZdVVfhhCJp9D7srvyJUPuvCnn4vfcw9uh37TOeaufCYqZDbHcHNXETrA8aujFoqFYWLi NSiq508UUkYoCqJlaq/qIkZ+rKcsO6P0iIRY46AtjOOrpVc6MvfExnNupQNU9z4IoZKKZV9m7oe8W Ov4S/hNayquzVTAQnngJmm6s8k0cycZ5PJXxGlRQWdjWUuq/aHWyYSydulYL37T5KOmKD9xBSuFmY LR0uRVvvidD1vrAtxwVg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mTOY5-00BXze-7A; Thu, 23 Sep 2021 13:14:01 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mTOY1-00BXyc-6w; Thu, 23 Sep 2021 13:13:58 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id 0E34A61164; Thu, 23 Sep 2021 13:13:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1632402836; bh=b7ciuEU81I/+7+Kcf5GtQcPnxHNd6AApdTsqk+hICIc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=b6dQij5uc96X0dTcnPcoUuxkPTLbF2fN2/4Y5WaYYhXJ6M2KOCv5+18SPDtUxEOMv JhsZevCeAarVQfrdBBLKmDTCCmizljQrOD2L/1iNv8E+2eF4KifI/fsdwvO+G0uLoF PgeaGsco1S9SgPDGj0lg6aesyAuewN/oXBER2PLk= Date: Thu, 23 Sep 2021 15:13:53 +0200 From: Greg KH To: Guo Zhi Cc: nsaenz@kernel.org, peterz@infradead.org, maz@kernel.org, bsegall@google.com, rdunlap@infradead.org, airlied@redhat.com, kan liang , odin@uged.al, bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-staging@lists.linux.dev, linux-kernel Subject: Re: [PATCH] staging: vchip_arm: Fix misuse of %x Message-ID: References: <20210923035554.669434-1-qtxuning1999@sjtu.edu.cn> <590112814.393656.1632401860257.JavaMail.zimbra@sjtu.edu.cn> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <590112814.393656.1632401860257.JavaMail.zimbra@sjtu.edu.cn> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210923_061357_332921_82444DF1 X-CRM114-Status: UNSURE ( 9.49 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org A: http://en.wikipedia.org/wiki/Top_post Q: Were do I find info about this thing called top-posting? A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? A: No. Q: Should I include quotations after my reply? http://daringfireball.net/2007/07/on_top On Thu, Sep 23, 2021 at 08:57:40PM +0800, Guo Zhi wrote: > We should restrict kernel pointer leakage issue by using kptr_restrict. > Therefore kernel pointers should be specified by %pK rather than %lx. I totally agree. What I am asking about is why is this message needed at all? Why not just remove the whole thing? Who uses it? thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel