From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Zhang Jiejing <jiejing.zhang@freescale.com>
Cc: suraj@atheros.com, marcel@holtmann.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: change gfp type in hci_recv_stream_fragment()
Date: Mon, 4 Apr 2011 18:16:17 -0300 [thread overview]
Message-ID: <20110404211617.GD2230@joana> (raw)
In-Reply-To: <1301554616-27595-1-git-send-email-jiejing.zhang@freescale.com>
Hi Zhang,
* Zhang Jiejing <jiejing.zhang@freescale.com> [2011-03-31 14:56:56 +0800]:
> change gfp type passed to hci_reassembly(), replace GFP_ATOMIC
> to GFP_KERNEL. Since some HCI_ACLDATA may request 1024+4 bytes
> some time GFP_ATOMIC will failed to allocation memory during
> large file FTP transfer in high baud rate.
>
> Signed-off-by: Zhang Jiejing <jiejing.zhang@freescale.com>
> ---
> net/bluetooth/hci_core.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c
> index 9c4541b..22b3ded 100644
> --- a/net/bluetooth/hci_core.c
> +++ b/net/bluetooth/hci_core.c
> @@ -1214,7 +1214,7 @@ int hci_recv_stream_fragment(struct hci_dev *hdev, void *data, int count)
> type = bt_cb(skb)->pkt_type;
>
> rem = hci_reassembly(hdev, type, data,
> - count, STREAM_REASSEMBLY, GFP_ATOMIC);
> + count, STREAM_REASSEMBLY, GFP_KERNEL);
We can't use GFP_KERNEL in a interrupt context, we can't sleep here and
GFP_ATOMIC guarantees that.
--
Gustavo F. Padovan
http://profusion.mobi
next prev parent reply other threads:[~2011-04-04 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 6:56 [PATCH] Bluetooth: change gfp type in hci_recv_stream_fragment() Zhang Jiejing
2011-04-04 21:16 ` Gustavo F. Padovan [this message]
2011-04-05 8:47 ` Zhang Jiejing-B33651
2011-04-05 12:02 ` Suraj Sumangala
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=20110404211617.GD2230@joana \
--to=padovan@profusion.mobi \
--cc=jiejing.zhang@freescale.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=suraj@atheros.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.