[PATCH] [v3] ieee802154: ca8210: Fix a potential UAF in ca8210_probe

2023-09-30 Thread Dinghao Liu
If of_clk_add_provider() fails in ca8210_register_ext_clock(), it calls clk_unregister() to release priv->clk and returns an error. However, the caller ca8210_probe() then calls ca8210_remove(), where priv->clk is freed again in ca8210_unregister_ext_clock(). In this case, a use-after-free may

Re: [PATCH 09/13] arm64: dts: qcom: msm8916-longcheer-l8150: Add sound and modem

2023-09-30 Thread Stephan Gerhold
On Tue, Sep 26, 2023 at 08:59:52PM +0200, Konrad Dybcio wrote: > On 26.09.2023 18:51, Stephan Gerhold wrote: > > From: Nikita Travkin > > > > Enable sound and modem for the Longcheer L8150 (e.g. Wileyfox Swift). > e.g. -> i.e., or is that thing sold under many labels? > Yes, "e.g." is indeed

Re: [PATCH] eventfs: Test for dentries array allocated in eventfs_release()

2023-09-30 Thread Google
On Sat, 30 Sep 2023 09:01:06 -0400 Steven Rostedt wrote: > From: "Steven Rostedt (Google)" > > The dcache_dir_open_wrapper() could be called when a dynamic event is > being deleted leaving a dentry with no children. In this case the > dlist->dentries array will never be allocated. This needs

Re: [PATCH 1/2] dt-bindings: mfd: qcom,spmi-pmic: Update gpio example

2023-09-30 Thread Krzysztof Kozlowski
On 29/09/2023 10:17, Luca Weiss wrote: > As per commit ea25d61b448a ("arm64: dts: qcom: Use plural _gpios node > label for PMIC gpios") all dts files now use the plural _gpios instead > of the singular _gpio as label. Update the schema example also to match. > > Signed-off-by: Luca Weiss > --- >

Re: [PATCH 1/3] dt-bindings: i2c: qcom-cci: Document SC7280 compatible

2023-09-30 Thread Krzysztof Kozlowski
On 29/09/2023 10:01, Luca Weiss wrote: > Document the compatible for the CCI block found on SC7280 SoC. > > Signed-off-by: Luca Weiss > --- > Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git

[PATCH] eventfs: Test for dentries array allocated in eventfs_release()

2023-09-30 Thread Steven Rostedt
From: "Steven Rostedt (Google)" The dcache_dir_open_wrapper() could be called when a dynamic event is being deleted leaving a dentry with no children. In this case the dlist->dentries array will never be allocated. This needs to be checked for in eventfs_release(), otherwise it will trigger a

[ANNOUNCE] 4.19.295-rt129

2023-09-30 Thread Daniel Wagner
Hello RT-list! I'm pleased to announce the 4.19.295-rt129 stable release. This is just an update to the v4.19.295 stable release. No RT specific changes. You can get this release via the git tree at: git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git branch: v4.19-rt

Re: [PATCH] tracing/eprobe: drop unneeded breaks

2023-09-30 Thread Google
On Fri, 29 Sep 2023 13:37:08 +0200 (CEST) Julia Lawall wrote: > > > On Fri, 29 Sep 2023, Masami Hiramatsu wrote: > > > On Thu, 28 Sep 2023 12:43:34 +0200 > > Julia Lawall wrote: > > > > > Drop break after return. > > > > > > > Good catch! This looks good to me. > > > > Acked-by: Masami

Re: [PATCH v5 00/12] tracing: fprobe: rethook: Use ftrace_regs instead of pt_regs

2023-09-30 Thread Google
On Fri, 29 Sep 2023 17:12:07 -0700 Alexei Starovoitov wrote: > On Thu, Sep 28, 2023 at 6:21 PM Masami Hiramatsu wrote: > > > > > > Thus, what I need is to make fprobe to use function-graph tracer's shadow > > stack and trampoline instead of rethook. This may need to generalize its > > interface

Re: [PATCH] trace: tracing_event_filter: fast path when no subsystem filters

2023-09-30 Thread Steven Rostedt
On Tue, 26 Sep 2023 10:20:58 -0400 Nicholas Lowell wrote: > From: Nicholas Lowell > > If there are no filters in the event subsystem, then there's no > reason to continue and hit the potentially time consuming > tracepoint_synchronize_unregister function. This should give > a speed up for

Re: [PATCH] ring-buffer: Update "shortest_full" in polling

2023-09-30 Thread Julia Lawall
On Fri, 29 Sep 2023, Steven Rostedt wrote: > From: "Steven Rostedt (Google)" > > It was discovered that the ring buffer polling was incorrectly stating > that read would not block, but that's because polling did not take into > account that reads will block if the "buffer-percent" was set.