From: jeffy <jeffy.chen@rock-chips.com>
To: Brian Norris <briannorris@chromium.org>
Cc: linux-bluetooth@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Johan Hedberg <johan.hedberg@intel.com>,
Peter Hurley <peter@hurleysoftware.com>,
Johan Hedberg <johan.hedberg@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>
Subject: Re: [PATCH 1/3] Bluetooth: bnep: fix possible might sleep error in bnep_session
Date: Mon, 13 Feb 2017 12:13:00 +0800 [thread overview]
Message-ID: <58A1324C.9070205@rock-chips.com> (raw)
In-Reply-To: <20170211014044.GB101282@google.com>
Hi brian,
On 02/11/2017 09:40 AM, Brian Norris wrote:
> Hi,
>
> On Tue, Jan 24, 2017 at 12:07:49PM +0800, Jeffy Chen wrote:
>> It looks like bnep_session has same pattern as the issue reported in
>> old rfcomm:
>>
>> while (1) {
>> set_current_state(TASK_INTERRUPTIBLE);
>> if (condition)
>> break;
>> // may call might_sleep here
>> schedule();
>> }
>> __set_current_state(TASK_RUNNING);
>>
>> Which fixed at:
>> dfb2fae Bluetooth: Fix nested sleeps
>>
>> So let's fix it at the same way, also follow the suggestion of:
>> https://lwn.net/Articles/628628/
>>
>> Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
>> ---
>>
>> net/bluetooth/bnep/core.c | 15 +++++++++------
>> 1 file changed, 9 insertions(+), 6 deletions(-)
>>
>> diff --git a/net/bluetooth/bnep/core.c b/net/bluetooth/bnep/core.c
>> index fbf251f..da04d51 100644
>> --- a/net/bluetooth/bnep/core.c
>> +++ b/net/bluetooth/bnep/core.c
>> @@ -484,16 +484,16 @@ static int bnep_session(void *arg)
>> struct net_device *dev = s->dev;
>> struct sock *sk = s->sock->sk;
>> struct sk_buff *skb;
>> - wait_queue_t wait;
>> + DEFINE_WAIT_FUNC(wait, woken_wake_function);
>>
>> BT_DBG("");
>>
>> set_user_nice(current, -15);
>>
>> - init_waitqueue_entry(&wait, current);
>> add_wait_queue(sk_sleep(sk), &wait);
>> while (1) {
>> - set_current_state(TASK_INTERRUPTIBLE);
>> + /* Ensure session->terminate is updated */
>> + smp_mb__before_atomic();
>>
>> if (atomic_read(&s->terminate))
>> break;
>> @@ -515,9 +515,8 @@ static int bnep_session(void *arg)
>> break;
>> netif_wake_queue(dev);
>>
>> - schedule();
>> + wait_woken(&wait, TASK_INTERRUPTIBLE, MAX_SCHEDULE_TIMEOUT);
>> }
>> - __set_current_state(TASK_RUNNING);
>> remove_wait_queue(sk_sleep(sk), &wait);
>>
>> /* Cleanup session */
>> @@ -666,7 +665,11 @@ int bnep_del_connection(struct bnep_conndel_req *req)
>> s = __bnep_get_session(req->dst);
>> if (s) {
>> atomic_inc(&s->terminate);
>> - wake_up_process(s->task);
>> +
>> + /* Ensure session->terminate is updated */
>> + smp_mb__after_atomic();
>> +
> __wake_up() suggests:
>
> * It may be assumed that this function implies a write memory barrier before
> * changing the task state if and only if any tasks are woken up.
>
> so the above barrier is probably unnecessary. I'm not so sure about the
> one before atomic_read(); seems fine.
Got it, thanx!
>
> Other than that, I this looks ok:
>
> Reviewed-by: Brian Norris <briannorris@chromium.or>
>
> But I haven't been testing BNEP.
>
> Brian
>
>> + wake_up_interruptible(sk_sleep(s->sock->sk));
>> } else
>> err = -ENOENT;
>>
>> --
>> 2.1.4
>>
>>
>
>
prev parent reply other threads:[~2017-02-13 4:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 4:07 [PATCH 1/3] Bluetooth: bnep: fix possible might sleep error in bnep_session Jeffy Chen
2017-01-24 4:07 ` [PATCH 2/3] Bluetooth: cmtp: fix possible might sleep error in cmtp_session Jeffy Chen
2017-02-11 1:43 ` Brian Norris
2017-02-13 4:14 ` jeffy
2017-01-24 4:07 ` [PATCH 3/3] Bluetooth: hidp: fix possible might sleep error in hidp_session_thread Jeffy Chen
2017-02-11 1:26 ` Brian Norris
2017-02-11 1:26 ` Brian Norris
2017-02-13 4:16 ` jeffy
2017-02-11 1:40 ` [PATCH 1/3] Bluetooth: bnep: fix possible might sleep error in bnep_session Brian Norris
2017-02-13 4:13 ` jeffy [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=58A1324C.9070205@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=dianders@chromium.org \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=johan.hedberg@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=peter@hurleysoftware.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.