[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180119172629.GD21673@breakpoint.cc>
Date: Fri, 19 Jan 2018 18:26:29 +0100
From: Florian Westphal <fw@...len.de>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Florian Westphal <fw@...len.de>, target-devel@...r.kernel.org,
mchristi@...hat.com, nab@...ux-iscsi.org, netdev@...r.kernel.org,
linux-scsi@...r.kernel.org
Subject: Re: [PATCH target-pending] iscsi-target: make sure to wake up
sleeping login worker
Eric Dumazet <eric.dumazet@...il.com> wrote:
> On Fri, 2018-01-19 at 14:36 +0100, Florian Westphal wrote:
> > diff --git a/drivers/target/iscsi/iscsi_target_nego.c b/drivers/target/iscsi/iscsi_target_nego.c
> > index b686e2ce9c0e..3723f8f419aa 100644
> > --- a/drivers/target/iscsi/iscsi_target_nego.c
> > +++ b/drivers/target/iscsi/iscsi_target_nego.c
> > @@ -432,6 +432,9 @@ static void iscsi_target_sk_data_ready(struct sock *sk)
> > if (test_and_set_bit(LOGIN_FLAGS_READ_ACTIVE, &conn->login_flags)) {
> > write_unlock_bh(&sk->sk_callback_lock);
> > pr_debug("Got LOGIN_FLAGS_READ_ACTIVE=1, conn: %p >>>>\n", conn);
> > + if (WARN_ON(iscsi_target_sk_data_ready == conn->orig_data_ready))
> > + return;
>
> Is this WARN_ON() belonging to this fix ?
> At least make it WARN_ON_ONCE() or pr_err_once()
Nicholas, I don't know this code at all so it would be good if you could
give advice here (omit all together, WARN_ON_ONCE, ...).
Thanks!
Powered by blists - more mailing lists