From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Benjamin Romer <benjamin.romer@unisys.com>,
David Kershner <david.kershner@unisys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, sparmaintainer@unisys.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: unisys: uislib: uisqueue.c: fixed sparse warning of context imbalance
Date: Tue, 2 Sep 2014 20:44:27 +0530 [thread overview]
Message-ID: <20140902151427.GA11966@sudip-PC> (raw)
In-Reply-To: <20140902140532.GD6600@mwanda>
On Tue, Sep 02, 2014 at 05:05:32PM +0300, Dan Carpenter wrote:
> On Tue, Sep 02, 2014 at 04:39:47PM +0530, Sudip Mukherjee wrote:
> > fixed sparse warning : context imbalance in 'do_locked_client_insert'
> > different lock contexts for basic block
> >
> > spin_unlock_irqrestore is called at a later stage before returning
> > from the function if locked is 1.
> >
> > Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
>
> This doesn't match the email address you are using.
>
for all my patch the Signed-off email address is different from the From email address.
I am not sure if I should do that, but since no one pointed it out so I guessed it is ok.
> Really, your patch isn't bad but I would prefer if you re-wrote this
> entire function because currently it is garbage.
>
> static u8
> do_locked_client_insert(struct uisqueue_info *queueinfo,
> unsigned int whichqueue,
> void *pSignal,
> spinlock_t *lock,
> unsigned char issueInterruptIfEmpty,
> u64 interruptHandle, u8 *channelId)
> {
> unsigned long flags;
> unsigned char queueWasEmpty;
>
> spin_lock_irqsave(lock, flags);
>
> if (!ULTRA_CHANNEL_CLIENT_ACQUIRE_OS(queueinfo->chan, channelId, NULL))
> goto unlock;
>
> queueWasEmpty = visor_signalqueue_empty(queueinfo->chan, whichqueue);
> if (!visor_signal_insert(queueinfo->chan, whichqueue, pSignal))
> goto release;
> ULTRA_CHANNEL_CLIENT_RELEASE_OS(queueinfo->chan, channelId, NULL);
> spin_unlock_irqrestore(lock, flags);
>
> queueinfo->packets_sent++;
>
> return 1;
>
> release:
> ULTRA_CHANNEL_CLIENT_RELEASE_OS(queueinfo->chan, channelId, NULL);
> unlock:
> spin_unlock_irqrestore(lock, flags);
>
> return 0;
> }
>
> The queueWasEmpty variable is kind of silly. It should just be an int
> or maybe a bool if you are being pedantic but instead we very
> specifically set it to be an unsigned variable of the incorrect type.
> Also we don't use queueWasEmpty at all. I think we could delete it...
>
> The problem with the original code was that the error paths and the
> success paths were mixed together like spaghetti. If you separate them
> out and unwind in the proper order with normal label names then the
> code is easy to understand.
>
> regards,
> dan carpenter
>
I will send a modified patch with the required changes.
thanks
sudip
next prev parent reply other threads:[~2014-09-02 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 11:09 [PATCH] staging: unisys: uislib: uisqueue.c: fixed sparse warning of context imbalance Sudip Mukherjee
2014-09-02 14:05 ` Dan Carpenter
2014-09-02 15:14 ` Sudip Mukherjee [this message]
2014-09-02 15:23 ` Dan Carpenter
2014-09-02 16:58 ` Sudip Mukherjee
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=20140902151427.GA11966@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=benjamin.romer@unisys.com \
--cc=dan.carpenter@oracle.com \
--cc=david.kershner@unisys.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparmaintainer@unisys.com \
/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