From: Greg KH <gregkh@linuxfoundation.org>
To: Ekansh Gupta <quic_ekangupt@quicinc.com>
Cc: srinivas.kandagatla@linaro.org, linux-arm-msm@vger.kernel.org,
quic_bkumar@quicinc.com, linux-kernel@vger.kernel.org,
quic_chennak@quicinc.com, dri-devel@lists.freedesktop.org,
arnd@arndb.de
Subject: Re: [PATCH v1] misc: fastrpc: Add support for multiple PD from one process
Date: Wed, 3 Jul 2024 12:39:16 +0200 [thread overview]
Message-ID: <2024070353-giggly-stardom-7b6d@gregkh> (raw)
In-Reply-To: <20240703065200.1438145-1-quic_ekangupt@quicinc.com>
On Wed, Jul 03, 2024 at 12:22:00PM +0530, Ekansh Gupta wrote:
> @@ -268,6 +272,7 @@ struct fastrpc_channel_ctx {
> struct fastrpc_session_ctx session[FASTRPC_MAX_SESSIONS];
> spinlock_t lock;
> struct idr ctx_idr;
> + struct ida dsp_pgid_ida;
You have an idr and an ida? Why two different types for the same
driver?
> struct list_head users;
> struct kref refcount;
> /* Flag if dsp attributes are cached */
> @@ -299,6 +304,7 @@ struct fastrpc_user {
> struct fastrpc_buf *init_mem;
>
> int tgid;
> + int dsp_pgid;
Are you sure this fits in an int?
> +static int fastrpc_pgid_alloc(struct fastrpc_channel_ctx *cctx)
> +{
> + int ret = -1;
No need to initialize this.
> +
> + /* allocate unique id between MIN_FRPC_PGID and MAX_FRPC_PGID */
> + ret = ida_alloc_range(&cctx->dsp_pgid_ida, MIN_FRPC_PGID,
> + MAX_FRPC_PGID, GFP_ATOMIC);
> + if (ret < 0)
> + return -1;
Why is -1 a specific value here? Return a real error please.
Or return 0 if that's not allowed.
v
> +
> + return ret;
> +}
> +
> static int fastrpc_device_open(struct inode *inode, struct file *filp)
> {
> struct fastrpc_channel_ctx *cctx;
> @@ -1582,6 +1605,12 @@ static int fastrpc_device_open(struct inode *inode, struct file *filp)
> fl->cctx = cctx;
> fl->is_secure_dev = fdevice->secure;
>
> + fl->dsp_pgid = fastrpc_pgid_alloc(cctx);
> + if (fl->dsp_pgid == -1) {
> + dev_dbg(&cctx->rpdev->dev, "too many fastrpc clients, max %u allowed\n", MAX_DSP_PD);
> + return -EUSERS;
Why -EUSERS?
And you obviously did not test this as you just leaked memory :(
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-03 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 6:52 Ekansh Gupta
2024-07-03 10:39 ` Greg KH [this message]
2024-07-04 6:17 ` Ekansh Gupta
2024-07-04 6:20 ` Ekansh Gupta
2024-07-04 6:40 ` Greg KH
2024-07-03 10:42 ` Dmitry Baryshkov
2024-07-04 6:27 ` Ekansh Gupta
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=2024070353-giggly-stardom-7b6d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bkumar@quicinc.com \
--cc=quic_chennak@quicinc.com \
--cc=quic_ekangupt@quicinc.com \
--cc=srinivas.kandagatla@linaro.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®