All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Sagi Maimon <maimon.sagi@gmail.com>,
	jonathan.lemon@gmail.com, richardcochran@gmail.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	Sagi Maimon <sagi.maimon@adtran.com>
Subject: Re: [PATCH v1] ptp: ocp: Fix NULL dereference in Adva board SMA sysfs operations
Date: Mon, 28 Apr 2025 16:16:13 +0100	[thread overview]
Message-ID: <58c1d1d4-d054-4aab-990b-e2083ceece4c@linux.dev> (raw)
In-Reply-To: <20250428143748.23729-1-maimon.sagi@gmail.com>

On 28/04/2025 15:37, Sagi Maimon wrote:
> From: Sagi Maimon <sagi.maimon@adtran.com>
> 
> On Adva boards, SMA sysfs store/get operations can call
> __handle_signal_outputs() or __handle_signal_inputs() while the `irig`
> and `dcf` pointers are uninitialized, leading to a NULL pointer
> dereference in __handle_signal() and causing a kernel crash. Add
> Adva-specific callbacks ptp_ocp_sma_adva_set_outputs() and
> ptp_ocp_sma_adva_set_inputs() to the ptp_ocp driver, and include NULL
> checks for `irig` and `dcf` to prevent crashes.
> 
> Fixes: ef61f5528fca ("ptp: ocp: add Adva timecard support")
> Signed-off-by: Sagi Maimon <sagi.maimon@adtran.com>
> ---
>   drivers/ptp/ptp_ocp.c | 62 +++++++++++++++++++++++++++++++++++++++++--
>   1 file changed, 60 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/ptp/ptp_ocp.c b/drivers/ptp/ptp_ocp.c
> index faf6e027f89a..3eaa2005b3b2 100644
> --- a/drivers/ptp/ptp_ocp.c
> +++ b/drivers/ptp/ptp_ocp.c
> @@ -2578,12 +2578,70 @@ static const struct ocp_sma_op ocp_fb_sma_op = {
>   	.set_output	= ptp_ocp_sma_fb_set_output,
>   };
>   
> +static int
> +ptp_ocp_sma_adva_set_output(struct ptp_ocp *bp, int sma_nr, u32 val)
> +{
> +	u32 reg, mask, shift;
> +	unsigned long flags;
> +	u32 __iomem *gpio;
> +
> +	gpio = sma_nr > 2 ? &bp->sma_map1->gpio2 : &bp->sma_map2->gpio2;
> +	shift = sma_nr & 1 ? 0 : 16;
> +
> +	mask = 0xffff << (16 - shift);
> +
> +	spin_lock_irqsave(&bp->lock, flags);
> +
> +	reg = ioread32(gpio);
> +	reg = (reg & mask) | (val << shift);
> +
> +	if (bp->irig_out)
> +		ptp_ocp_irig_out(bp, reg & 0x00100010);
> +	if (bp->dcf_out)
> +		ptp_ocp_dcf_out(bp, reg & 0x00200020);

You never initialize neither irig_out nor dcf_out, both checks will
always fail. Looks like a dead code - please, remove it.

> +
> +	iowrite32(reg, gpio);
> +
> +	spin_unlock_irqrestore(&bp->lock, flags);
> +
> +	return 0;
> +}
> +
> +static int
> +ptp_ocp_sma_adva_set_inputs(struct ptp_ocp *bp, int sma_nr, u32 val)
> +{
> +	u32 reg, mask, shift;
> +	unsigned long flags;
> +	u32 __iomem *gpio;
> +
> +	gpio = sma_nr > 2 ? &bp->sma_map2->gpio1 : &bp->sma_map1->gpio1;
> +	shift = sma_nr & 1 ? 0 : 16;
> +
> +	mask = 0xffff << (16 - shift);
> +
> +	spin_lock_irqsave(&bp->lock, flags);
> +
> +	reg = ioread32(gpio);
> +	reg = (reg & mask) | (val << shift);
> +
> +	if (bp->irig_in)
> +		ptp_ocp_irig_in(bp, reg & 0x00100010);
> +	if (bp->dcf_in)
> +		ptp_ocp_dcf_in(bp, reg & 0x00200020);

The same goes here - neither irig_in, nor dcf_in will have real values
for your hardware, please remove this checks.

> +
> +	iowrite32(reg, gpio);
> +
> +	spin_unlock_irqrestore(&bp->lock, flags);
> +
> +	return 0;
> +}
> +
>   static const struct ocp_sma_op ocp_adva_sma_op = {
>   	.tbl		= { ptp_ocp_adva_sma_in, ptp_ocp_adva_sma_out },
>   	.init		= ptp_ocp_sma_fb_init,
>   	.get		= ptp_ocp_sma_fb_get,
> -	.set_inputs	= ptp_ocp_sma_fb_set_inputs,
> -	.set_output	= ptp_ocp_sma_fb_set_output,
> +	.set_inputs	= ptp_ocp_sma_adva_set_inputs,
> +	.set_output	= ptp_ocp_sma_adva_set_output,
>   };
>   
>   static int

pw-bot: cr

  reply	other threads:[~2025-04-28 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28 14:37 [PATCH v1] ptp: ocp: Fix NULL dereference in Adva board SMA sysfs operations Sagi Maimon
2025-04-28 15:16 ` Vadim Fedorenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-28 14:33 Sagi Maimon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58c1d1d4-d054-4aab-990b-e2083ceece4c@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maimon.sagi@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=sagi.maimon@adtran.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.