mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Babanpreet Singh <bbnpreetsingh@gmail.com>
Cc: Srinivas Kandagatla <srini@kernel.org>,
	Vinod Koul <vkoul@kernel.org>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slimbus: qcom-ngd-ctrl: Release the TX descriptor on error paths
Date: Fri, 2 Oct 2026 08:20:21 +0200	[thread overview]
Message-ID: <2026100200-emphasis-overgrown-0a95@gregkh> (raw)
In-Reply-To: <20261001232520.7-1-bbnpreetsingh@gmail.com>

On Thu, Oct 01, 2026 at 11:25:20PM +0000, Babanpreet Singh wrote:
> Hi Srinivas,
> 
> Static analysis, then reading. smatch flagged the txn->msg check in
> qcom_slim_ngd_xfer_msg() and while I was looking at that function I
> noticed the two returns between tx_msg_get() and tx_msg_post(). I do not
> have a SLIMbus target. The -ENOMEM consequence in the commit message is
> derived from the code rather than observed: tx_head only moves in
> qcom_slim_ngd_tx_msg_dma_cb() and in the re-init path, so a descriptor
> that is claimed and never posted has no way back into the ring.
> 
> Verification was build only.
> 
> On the stable tag: I can send a v2 with Cc: stable and the "found by
> static analysis, compile tested only" wording.

We have no context here at all, please never top-post, as my bot says:


A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

      reply	other threads:[~2026-10-02  6:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  3:52 Babanpreet Singh
2026-09-15  5:33 ` Babanpreet Singh
2026-09-17 22:03 ` Srinivas Kandagatla
2026-10-01 23:25   ` Babanpreet Singh
2026-10-02  6:20     ` Greg Kroah-Hartman [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=2026100200-emphasis-overgrown-0a95@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bbnpreetsingh@gmail.com \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=srini@kernel.org \
    --cc=vkoul@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®