linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Cho <tony.cho@atmel.com>
To: Greg KH <gregkh@linuxfoundation.org>,
	Chandra S Gorentla <csgorentla@gmail.com>
Cc: <rachel.kim@atmel.com>, <devel@driverdev.osuosl.org>,
	<chris.park@atmel.com>, <linux-wireless@vger.kernel.org>,
	<johnny.kim@atmel.com>, <linux-kernel@vger.kernel.org>,
	<dan.carpenter@oracle.com>
Subject: Re: [PATCH 1/2] drivers: staging: wilc1000: Move spin lock to the start of critical section
Date: Mon, 5 Oct 2015 12:23:50 +0900	[thread overview]
Message-ID: <5611ED46.7040800@atmel.com> (raw)
In-Reply-To: <20151004084335.GA24589@kroah.com>



On 2015년 10월 04일 17:43, Greg KH wrote:
> On Sat, Oct 03, 2015 at 02:57:29PM +0530, Chandra S Gorentla wrote:
>> The spin_lock_irqsave is moved to just beginning of critical section.
>> This change moves a couple of return statements out of the lock.
>>
>> Signed-off-by: Chandra S Gorentla <csgorentla@gmail.com>
>> ---
>>   drivers/staging/wilc1000/wilc_msgqueue.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/staging/wilc1000/wilc_msgqueue.c b/drivers/staging/wilc1000/wilc_msgqueue.c
>> index d5ebd6d..284a3f5 100644
>> --- a/drivers/staging/wilc1000/wilc_msgqueue.c
>> +++ b/drivers/staging/wilc1000/wilc_msgqueue.c
>> @@ -72,8 +72,6 @@ int wilc_mq_send(WILC_MsgQueueHandle *pHandle,
>>   		goto ERRORHANDLER;
>>   	}
>>   
>> -	spin_lock_irqsave(&pHandle->strCriticalSection, flags);
>> -
>>   	/* construct a new message */
>>   	pstrMessage = kmalloc(sizeof(Message), GFP_ATOMIC);
> As you have moved the lock, can you also change this to GFP_KERNEL as
> well because we do not have a lock held?
>
> And how have you tested that this is ok?  What is this lock trying to
> protect?

This function is called even in interrupt context, so GFP_ATOMIC should be called. The spinlock
also should protect pstrMessage from allocating the memory, so we don't place it to the beginning
of critical section as Chandra said.

Thanks,
Tony.

> thanks,
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      parent reply	other threads:[~2015-10-05  3:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03  9:27 [PATCH 1/2] drivers: staging: wilc1000: Move spin lock to the start of critical section Chandra S Gorentla
2015-10-03  9:27 ` [PATCH 2/2] drivers: staging: wilc1000: Call kfree only for error cases Chandra S Gorentla
2015-10-04  8:44   ` Greg KH
2015-10-04  9:16     ` Dan Carpenter
2015-10-04 10:10       ` Greg KH
2015-10-04 10:28     ` Chandra Gorentla
2015-10-05  3:23       ` Tony Cho
2015-10-04  8:43 ` [PATCH 1/2] drivers: staging: wilc1000: Move spin lock to the start of critical section Greg KH
2015-10-04 10:07   ` Chandra Gorentla
2015-10-04 10:19     ` Greg KH
2015-10-05  3:23   ` Tony Cho [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=5611ED46.7040800@atmel.com \
    --to=tony.cho@atmel.com \
    --cc=chris.park@atmel.com \
    --cc=csgorentla@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johnny.kim@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rachel.kim@atmel.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;
as well as URLs for NNTP newsgroup(s).