Received-SPF: pass (google.com: domain of linux-kernel+bounces-104032-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
From: Thomas Gleixner <tglx@linutronix.de>
To: Enlin Mu <enlinmu@gmail.com>
Cc: Enlin Mu <enlin.mu@outlook.com>, linux-kernel@vger.kernel.org,
 enlin.mu@unisoc.com, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] hrtimer:Add get_hrtimer_cpu_base()
In-Reply-To: <CAAfh-jM6TSbFHUYCi0kC7JgszCaz=-So7+=at-aDfTSrOPjraQ@mail.gmail.com>
References: <TYSPR04MB7084FCAF74B4CFA30D386B698A2A2@TYSPR04MB7084.apcprd04.prod.outlook.com>
 <87cyrxm7ua.ffs@tglx>
 <CAAfh-jOu0hG1hfWX9kL_gOXkSLXEVGNkddP-azO=pjNAKsRGhA@mail.gmail.com>
 <877ci5m3c4.ffs@tglx>
 <CAAfh-jM6TSbFHUYCi0kC7JgszCaz=-So7+=at-aDfTSrOPjraQ@mail.gmail.com>
Date: Fri, 15 Mar 2024 04:41:59 +0100
Message-ID: <87h6h8kvp4.ffs@tglx>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 15 2024 at 11:12, Enlin Mu wrote:
> Thomas Gleixner <tglx@linutronix.de> =E4=BA=8E2024=E5=B9=B43=E6=9C=8814=
=E6=97=A5=E5=91=A8=E5=9B=9B 19:59=E5=86=99=E9=81=93=EF=BC=9A
>>
>> On Thu, Mar 14 2024 at 18:45, Enlin Mu wrote:
>> > Thomas Gleixner <tglx@linutronix.de> =E4=BA=8E2024=E5=B9=B43=E6=9C=881=
4=E6=97=A5=E5=91=A8=E5=9B=9B 18:22=E5=86=99=E9=81=93=EF=BC=9A
>> >>
>> >> On Wed, Mar 13 2024 at 05:30, Enlin Mu wrote:
>> >> > From: Enlin Mu <enlin.mu@unisoc.com>
>> >> >
>> >> > On the Arm platform,arch_timer may occur irq strom,
>> >> > By using the next_timer of hrtimer_cpu_base, it is
>> >> > possible to quickly locate abnormal timers.
>> >> > As it is an out of tree modules,the function needs
>> >> > to be exproted.
>> >>
>> >> No. We are not exporting for out of tree code.
>> > Can you explain it?
>>
>> Exporting functions or variables requires an in tree usecase.
>
> OK, Thanks, I  got it.

No, you did not get it at all.

Q: Where is the actual in kernel use case which utilizes the exported
   symbol in a module?

A: There is still none.

For further clarification there will be none ever because you are
violating all encapsulation rules of the kernel subsytems without
providing at least an attempt of justification.

Nothing outside of the timer core subsystem has any business to fiddle
with this data structure ever. Period.