From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: outreachy-kernel@googlegroups.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
David Kershner <david.kershner@unisys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [Outreachy kernel] [PATCH v3] staging: unisys: visorhba: Convert module from IDR to XArray
Date: Mon, 26 Apr 2021 23:15:40 +0200 [thread overview]
Message-ID: <107967147.Ip005GxVp3@linux.local> (raw)
In-Reply-To: <20210426192101.GQ235567@casper.infradead.org>
On Monday, April 26, 2021 9:21:01 PM CEST Matthew Wilcox wrote:
> On Mon, Apr 26, 2021 at 08:42:45PM +0200, Fabio M. De Francesco wrote:
> > +static void setup_scsitaskmgmt_handles(struct xarray *xa, struct
uiscmdrsp *cmdrsp,
> >
> > wait_queue_head_t *event,
int *result)
> >
> > {
> >
> > - /* specify the event that has to be triggered when this */
> > - /* cmd is complete */
> > - cmdrsp->scsitaskmgmt.notify_handle =
> > - simple_idr_get(idrtable, event, lock);
> > - cmdrsp->scsitaskmgmt.notifyresult_handle =
> > - simple_idr_get(idrtable, result, lock);
> > + u32 id;
> > + int ret;
> > +
> > + /* specify the event that has to be triggered when this cmd is
complete */
> > + id = (u32)cmdrsp->scsitaskmgmt.notify_handle;
> > + ret = xa_alloc_irq(xa, &id, event, XA_LIMIT(1, INT_MAX),
GFP_KERNEL);
>
> OK, think this one through a bit. When xa_alloc_irq() stores the ID that
> it assigned into 'id', what happens to it next?
>
Oh, I overlooked that... The ID in 'id' is lost when the function exits and
the stack frame is unwound.
Now I have another problem: xa_alloc_irq() writes id u32* but I have an u64*
in 'id'. What happens if I cast 'id' to an u32* when passing it to
xa_alloc_irq()?
u64 *id;
int ret;
id = &cmdrsp->scsitaskmgmt.notify_handle;
ret = xa_alloc_irq(xa, (u32 *)id, event, XA_LIMIT(1, INT_MAX), GFP_KERNEL);
Do I destroy the information stored in 'id' with that cast?
>
> > + id = (u32)cmdrsp->scsitaskmgmt.notifyresult_handle;
> > + ret = xa_alloc_irq(xa, &id, result, XA_LIMIT(1, INT_MAX),
GFP_KERNEL);
> >
> > }
> >
> > @@ -1053,8 +1018,6 @@ static int visorhba_probe(struct visor_device *dev)
> >
> > if (err)
> >
> > goto err_debugfs_info;
> >
> > - idr_init(&devdata->idr);
>
> You still need to initialise the XArray, either with xa_init() or by
> using DEFINE_XARRAY. Since it's dynamically allocated, the former is
> correct.
>
I had read that XArray must be initialized with xa_init(). However, when I
deleted the line with the initialization of the IDR, I forgot to replace it
with a statement that uses xa_init().
Thanks,
Fabio
next prev parent reply other threads:[~2021-04-26 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 18:42 [Outreachy kernel] [PATCH v3] staging: unisys: visorhba: Convert module from IDR to XArray Fabio M. De Francesco
2021-04-26 19:21 ` Matthew Wilcox
2021-04-26 21:15 ` Fabio M. De Francesco [this message]
2021-04-26 22:03 ` Matthew Wilcox
2021-04-27 11:59 ` Fabio M. De Francesco
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=107967147.Ip005GxVp3@linux.local \
--to=fmdefrancesco@gmail.com \
--cc=daniel@ffwll.ch \
--cc=david.kershner@unisys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy-kernel@googlegroups.com \
--cc=willy@infradead.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 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.