From: Michal Nazarewicz <mina86@mina86.com>
To: Tapasweni Pathak <tapaswenipathak@gmail.com>,
balbi@ti.com, gregkh@linuxfoundation.org, r.baldyga@samsung.com,
andrzej.p@samsung.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: tapaswenipathak@gmail.com, julia.lawall@lip6.fr
Subject: Re: [PATCH] usb: gadget: function: Replace GFP_KERNEL with GFP_ATOMIC
Date: Fri, 20 Feb 2015 18:09:32 +0100 [thread overview]
Message-ID: <xa1tegpk4iib.fsf@mina86.com> (raw)
In-Reply-To: <20150220130524.GA22598@kt-Inspiron-3542>
On Fri, Feb 20 2015, Tapasweni Pathak wrote:
> To avoid deadlock, do not call blocking functions with spinlocks held.
>
> Replace GFP_KERNEL with GFP_ATOMIC, as the latter will fail if the heap
> doesn't have enough free pages but will not sleep and hence deadlock can
> be avoided.
>
> Found by Coccinelle.
>
> Signed-off-by: Tapasweni Pathak <tapaswenipathak@gmail.com>
> ---
> Is there any other way this can be fixed as it is better to avoid GFP_ATOMIC?
I think there is. A patchset will follow this reply.
> drivers/usb/gadget/function/f_fs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/gadget/function/f_fs.c b/drivers/usb/gadget/function/f_fs.c
> index af98b09..8a25d30 100644
> --- a/drivers/usb/gadget/function/f_fs.c
> +++ b/drivers/usb/gadget/function/f_fs.c
> @@ -823,7 +823,7 @@ static ssize_t ffs_epfile_io(struct file *file, struct ffs_io_data *io_data)
> }
>
> if (io_data->aio) {
> - req = usb_ep_alloc_request(ep->ep, GFP_KERNEL);
> + req = usb_ep_alloc_request(ep->ep, GFP_ATOMIC);
> if (unlikely(!req))
> goto error_lock;
>
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
prev parent reply other threads:[~2015-02-20 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 13:05 [PATCH] usb: gadget: function: Replace GFP_KERNEL with GFP_ATOMIC Tapasweni Pathak
2015-02-20 17:09 ` Michal Nazarewicz [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=xa1tegpk4iib.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=r.baldyga@samsung.com \
--cc=tapaswenipathak@gmail.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 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.