public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel•org>
To: Alex Elder <elder@linaro•org>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
	pabeni@redhat•com, mka@chromium•org, andersson@kernel•org,
	quic_cpratapa@quicinc•com, quic_avuyyuru@quicinc•com,
	quic_jponduru@quicinc•com, quic_subashab@quicinc•com,
	elder@kernel•org, netdev@vger•kernel.org,
	linux-arm-msm@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH] net: ipa: don't overrun IPA suspend interrupt registers
Date: Mon, 19 Feb 2024 19:44:33 +0000	[thread overview]
Message-ID: <20240219194433.GN40273@kernel.org> (raw)
In-Reply-To: <20240218190450.331390-1-elder@linaro.org>

On Sun, Feb 18, 2024 at 01:04:50PM -0600, Alex Elder wrote:
> In newer hardware, IPA supports more than 32 endpoints.  Some
> registers--such as IPA interrupt registers--represent endpoints
> as bits in a 4-byte register, and such registers are repeated as
> needed to represent endpoints beyond the first 32.
> 
> In ipa_interrupt_suspend_clear_all(), we clear all pending IPA
> suspend interrupts by reading all status register(s) and writing
> corresponding registers to clear interrupt conditions.
> 
> Unfortunately the number of registers to read/write is calculated
> incorrectly, and as a result we access *many* more registers than
> intended.  This bug occurs only when the IPA hardware signals a
> SUSPEND interrupt, which happens when a packet is received for an
> endpoint (or its underlying GSI channel) that is suspended.  This
> situation is difficult to reproduce, but possible.

I see what you mean about *many* more :)

> Fix this by correctly computing the number of interrupt registers to
> read and write.  This is the only place in the code where registers
> that map endpoints or channels this way perform this calculation.
> 
> Fixes: f298ba785e2d ("net: ipa: add a parameter to suspend registers")
> Signed-off-by: Alex Elder <elder@linaro•org>

As noted by Alex elsewhere elsewhere in this thread, this is for net.

Reviewed-by: Simon Horman <horms@kernel•org>

      parent reply	other threads:[~2024-02-19 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 19:04 [PATCH] net: ipa: don't overrun IPA suspend interrupt registers Alex Elder
2024-02-18 19:07 ` Alex Elder
2024-02-19 19:44 ` Simon Horman [this message]

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=20240219194433.GN40273@kernel.org \
    --to=horms@kernel$(echo .)org \
    --cc=andersson@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=elder@kernel$(echo .)org \
    --cc=elder@linaro$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-arm-msm@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=mka@chromium$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=quic_avuyyuru@quicinc$(echo .)com \
    --cc=quic_cpratapa@quicinc$(echo .)com \
    --cc=quic_jponduru@quicinc$(echo .)com \
    --cc=quic_subashab@quicinc$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox