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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E1F47C77B7A for ; Tue, 30 May 2023 08:16:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230129AbjE3IQZ (ORCPT ); Tue, 30 May 2023 04:16:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34486 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230133AbjE3IQR (ORCPT ); Tue, 30 May 2023 04:16:17 -0400 Received: from mailout4.samsung.com (mailout4.samsung.com [203.254.224.34]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B80159D for ; Tue, 30 May 2023 01:16:09 -0700 (PDT) Received: from epcas5p4.samsung.com (unknown [182.195.41.42]) by mailout4.samsung.com (KnoxPortal) with ESMTP id 20230530081605epoutp04cd1b2c62c05f81c55fb5da583ca9faff~j3c62H3RY1503515035epoutp04X for ; Tue, 30 May 2023 08:16:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout4.samsung.com 20230530081605epoutp04cd1b2c62c05f81c55fb5da583ca9faff~j3c62H3RY1503515035epoutp04X DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1685434565; bh=5ac7mcvUjipTjuyt2bSsLImVDWiscD6gA99NQK48iBs=; h=Subject:Reply-To:From:To:CC:In-Reply-To:Date:References:From; b=Fnat8ZEMwWGH3IskToGqsOFf2j0fTLuLglIL46XCr39Wq+zqmZKhvm68EvCCpB/eW aX/OACM0Zbylw+ef6wgUCOYRWwkj/AB/VMK7pjBGqWCSIkglKUyDnp5yJQfgMR0taW k5L7RwARTUW5R0mk60USG/WlB9f4gMWnfGGaloC8= Received: from epsmges5p3new.samsung.com (unknown [182.195.42.75]) by epcas5p2.samsung.com (KnoxPortal) with ESMTP id 20230530081604epcas5p2a2caf81b1d6cb14d5bc0d5b3e3cd7b38~j3c50_WwG1821018210epcas5p2E; Tue, 30 May 2023 08:16:04 +0000 (GMT) X-AuditID: b6c32a4b-56fff70000013ffc-8e-6475b0c4a44d Received: from epcas5p1.samsung.com ( [182.195.41.39]) by epsmges5p3new.samsung.com (Symantec Messaging Gateway) with SMTP id E2.DF.16380.4C0B5746; Tue, 30 May 2023 17:16:04 +0900 (KST) Mime-Version: 1.0 Subject: RE: [PATCH 1/1] arch:hexagon/powerpc: use KSYM_NAME_LEN in array size Reply-To: maninder1.s@samsung.com Sender: Maninder Singh From: Maninder Singh To: Petr Mladek CC: Miguel Ojeda , "keescook@chromium.org" , Steven Rostedt , Masami Hiramatsu , "bcain@quicinc.com" , "mpe@ellerman.id.au" , "npiggin@gmail.com" , "christophe.leroy@csgroup.eu" , "nathanl@linux.ibm.com" , "ustavoars@kernel.org" , "alex.gaynor@gmail.com" , "gary@garyguo.net" , "ojeda@kernel.org" , "linux-hexagon@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" , Onkarnath , Wedson Almeida Filho X-Priority: 3 X-Content-Kind-Code: NORMAL In-Reply-To: X-Drm-Type: N,general X-Msg-Generator: Mail X-Msg-Type: PERSONAL X-Reply-Demand: N Message-ID: <20230530081405epcms5p879eeba2a521ff23fea57ce42bf913eac@epcms5p8> Date: Tue, 30 May 2023 13:44:05 +0530 X-CMS-MailID: 20230530081405epcms5p879eeba2a521ff23fea57ce42bf913eac Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Sendblock-Type: REQ_APPROVE CMS-TYPE: 105P X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPKsWRmVeSWpSXmKPExsWy7bCmuu6RDaUpBs39/BZ/Z29nt3i4u4XF 4s6k5+wWF8+8ZrQ4051r8b5lB5vF5V1z2Cx+f//HarF4uZrFzelv2C22NBxis9hwNNji54sb LBYr5y9ntFjR84HV4v/jr6wW+zoeMFn8f3eEyWLDsrWMDsIesxsusnh8vXmOyWPRywYWjyWd v5g8ds66y+7Rsu8Wu8emVZ1sHhMWHWD0OD9jIaPHxD11Hn1bVjF6rN9ylcXj8ya5AN4oLpuU 1JzMstQifbsErozlZz+yFDxhr2hduYCtgXETWxcjJ4eEgInE7cWHmboYuTiEBHYzSqy/NI+1 i5GDg1dAUOLvDmGQGmGBAIkFe5cygthCAooSF2asYQQpERYwkPi1VQMkzCagJ7Fq1x4WEFtE QEni1fy7zCAjmQU+s0msm7+bEWIXr8SM9qcsELa0xPblW8HinAKqEtdaVkPViErcXP2WHcZ+ f2w+VFxEovXeWWYIW1DiwU+YmTISqzf3Qs2slnj6+hwbyGIJgRZGiX27YYrMJdYvWcUO8Zev ROujFJAwC9Deb6smQpW4SJyfcpwVxGYWkJfY/nYOM0g5s4CmxPpd+hAlshJTT61jgijhk+j9 /YQJ5q0d82BsVYmWmxtYYV78/PEj1GkeEqe+r2KFBPNHJomJC1tYJzAqzEKE9Cwkm2chbF7A yLyKUTK1oDg3PbXYtMA4L7Vcrzgxt7g0L10vOT93EyM4TWp572B89OCD3iFGJg7GQ4wSHMxK Iry2icUpQrwpiZVVqUX58UWlOanFhxilOViUxHnVbU8mCwmkJ5akZqemFqQWwWSZODilGph4 csMjNTYyWj9Jr5oyo6Xxz/4UV6H/EpkTtXWlzR+u4+0ofvpVti9zTv9693aFR7KC+TWrNp3I Xfhv3/YEtk2rdA+HlTjf+Nrb7S2Qzb88bnFkUqDTFWWpV+zn3HeFlxf09jE0ZD9vzlzHkiR4 9XlfVeeXWTum2d2P8866cfDc0atZ1rdPCc5rdd3yz1Lh+/7bvUV+l29t7T+5q/mN0JGHn031 ohNmOS5Yep+nxHSf45y159r1vrrvvRS16sn0voYbOZErZZQPMTze/q6bTWuyuOTdvpK808fW bN0x596KYK0T/k6H415/m+msrtHQqHp8Ft+3ebPblquyztt4ZkPR5+7+u38qGIsPzu2V9tiq xFKckWioxVxUnAgAVvt/uAIEAAA= X-CMS-RootMailID: 20230529052832epcas5p4fa1b8cf25d9810d32bd2ccf012086fb3 References: <20230529052821.58175-1-maninder1.s@samsung.com> <20230529105707epcms5p1418eac680ebe1736196706b0db80dd39@epcms5p1> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Peter, > > The best solution would be to pass the buffer size as an extra > parameter. Especially when some code passes buffers that are > allocated/reserved dynamically. > > Sigh, I am not sure how many changes it would require in kallsyms > API and all the callers. But it would be really appreciated, IMHO. > yes we already prepared size changes 5-6 months back: https://lore.kernel.org/lkml/YonTOL4zC4CytVrn@infradead.org/t/ [PATCH 1/5] kallsyms: pass buffer size in sprint_* APIs But at that time new API development(for replacement of seq_buf) was in progress and we decided to wait for that completion. https://lore.kernel.org/r/20220604193042.1674951-2-kent.overstreet@gmail.com https://lore.kernel.org/r/20220604193042.1674951-4-kent.overstreet@gmail.com As I checeked these APIs are not pushed to mainline. we will try to prepare new patch set for kallsym changes again with seq_buf to take care of length argument. Thanks, Maninder Singh