The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: srini@kernel.org, linux-kernel@vger.kernel.org,
	Ling Xu <quic_lxu5@quicinc.com>,
	stable@kernel.org, Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH 1/4] misc: fastrpc: Save actual DMA size in fastrpc_map structure
Date: Fri, 12 Sep 2025 16:22:39 +0200	[thread overview]
Message-ID: <2025091212-umpire-large-b601@gregkh> (raw)
In-Reply-To: <31a37e24-0044-4987-89a9-d891200592ec@oss.qualcomm.com>

On Fri, Sep 12, 2025 at 04:30:37PM +0300, Dmitry Baryshkov wrote:
> On 12/09/2025 16:12, srini@kernel.org wrote:
> > From: Ling Xu <quic_lxu5@quicinc.com>
> > 
> > For user passed fd buffer, map is created using DMA calls. The
> > map related information is stored in fastrpc_map structure. The
> > actual DMA size is not stored in the structure. Store the actual
> > size of buffer and check it against the user passed size.
> > 
> > Fixes: c68cfb718c8f ("misc: fastrpc: Add support for context Invoke method")
> > Cc: stable@kernel.org
> > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> > Co-developed-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
> > Signed-off-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
> > Signed-off-by: Ling Xu <quic_lxu5@quicinc.com>
> > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > Signed-off-by: Srinivas Kandagatla <srini@kernel.org>
> > ---
> >   drivers/misc/fastrpc.c | 27 ++++++++++++++++++---------
> >   1 file changed, 18 insertions(+), 9 deletions(-)
> > 
> 
> Please use correct CC list when sending patches. You've missed several
> entries from the MAINTAINERS file.

This is just to send these patches for me for my tree, it's not really a
normal "review" as that should have already happened (based on the
signed-off-by chain above.)

thanks,
greg k-h

  reply	other threads:[~2025-09-12 14:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 13:12 [PATCH 0/4] fastrpc: fixes for 6.17 srini
2025-09-12 13:12 ` [PATCH 1/4] misc: fastrpc: Save actual DMA size in fastrpc_map structure srini
2025-09-12 13:30   ` Dmitry Baryshkov
2025-09-12 14:22     ` Greg KH [this message]
2025-09-12 15:21       ` Dmitry Baryshkov
2025-09-12 13:12 ` [PATCH 2/4] misc: fastrpc: Fix fastrpc_map_lookup operation srini
2025-09-12 13:12 ` [PATCH 3/4] misc: fastrpc: fix possible map leak in fastrpc_put_args srini
2025-09-12 13:12 ` [PATCH 4/4] misc: fastrpc: Skip reference for DMA handles srini

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=2025091212-umpire-large-b601@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=ekansh.gupta@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_lxu5@quicinc.com \
    --cc=srini@kernel.org \
    --cc=stable@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