From: Andrew Morton <akpm@linux-foundation.org>
To: Alexandre Bounine <alexandre.bounine@idt.com>
Cc: Alexey Khoroshilov <khoroshilov@ispras.ru>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] rapidio/rio_cm: avoid GFP_KERNEL in atomic context
Date: Fri, 16 Sep 2016 15:08:01 -0700 [thread overview]
Message-ID: <20160916150801.24b13aed1984dd37de21592c@linux-foundation.org> (raw)
In-Reply-To: <20160915175402.10122-1-alexandre.bounine@idt.com>
On Thu, 15 Sep 2016 13:54:02 -0400 Alexandre Bounine <alexandre.bounine@idt.com> wrote:
> As reported by Alexey Khoroshilov <khoroshilov@ispras.ru>
> (see https://lkml.org/lkml/2016/9/9/737):
> riocm_send_close() is called from rio_cm_shutdown() under
> spin_lock_bh(idr_lock), but riocm_send_close() uses a GFP_KERNEL
> allocation.
>
> Fix by taking riocm_send_close() outside of spinlock protected code.
>
> --- a/drivers/rapidio/rio_cm.c
> +++ b/drivers/rapidio/rio_cm.c
> @@ -2242,17 +2242,31 @@ static int rio_cm_shutdown(struct notifier_block *nb, unsigned long code,
> {
> struct rio_channel *ch;
> unsigned int i;
> + LIST_HEAD(list);
>
> riocm_debug(EXIT, ".");
>
> + /*
> + * If there are any channels left in connected state send
> + * close notification to the connection partner.
> + * First build a list of channels that require a closing
> + * notification because function riocm_send_close() should
> + * be called outside of spinlock protected code.
> + */
> spin_lock_bh(&idr_lock);
> idr_for_each_entry(&ch_idr, ch, i) {
> - riocm_debug(EXIT, "close ch %d", ch->id);
> - if (ch->state == RIO_CM_CONNECTED)
> - riocm_send_close(ch);
> + if (ch->state == RIO_CM_CONNECTED) {
> + riocm_debug(EXIT, "close ch %d", ch->id);
> + idr_remove(&ch_idr, ch->id);
> + list_add(&ch->ch_node, &list);
> + }
> }
> spin_unlock_bh(&idr_lock);
>
> + if (!list_empty(&list))
> + list_for_each_entry(ch, &list, ch_node)
> + riocm_send_close(ch);
> +
> return NOTIFY_DONE;
> }
Fair enough.
Can we remove the !list_empty() test?
--- a/drivers/rapidio/rio_cm.c~rapidio-rio_cm-avoid-gfp_kernel-in-atomic-context-fix
+++ a/drivers/rapidio/rio_cm.c
@@ -2268,9 +2268,8 @@ static int rio_cm_shutdown(struct notifi
}
spin_unlock_bh(&idr_lock);
- if (!list_empty(&list))
- list_for_each_entry(ch, &list, ch_node)
- riocm_send_close(ch);
+ list_for_each_entry(ch, &list, ch_node)
+ riocm_send_close(ch);
return NOTIFY_DONE;
}
_
next prev parent reply other threads:[~2016-09-16 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 17:54 Alexandre Bounine
2016-09-16 22:08 ` Andrew Morton [this message]
2016-09-19 14:05 ` Bounine, Alexandre
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=20160916150801.24b13aed1984dd37de21592c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alexandre.bounine@idt.com \
--cc=khoroshilov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®