[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5A6173F7.2050905@redhat.com>
Date: Thu, 18 Jan 2018 22:28:39 -0600
From: Mike Christie <mchristi@...hat.com>
To: Florian Westphal <fw@...len.de>,
"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
Cc: target-devel <target-devel@...r.kernel.org>,
Linux-netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>
Subject: Re: iscsi target regression due to "tcp: remove prequeue support"
patch
On 01/18/2018 09:10 AM, Florian Westphal wrote:
>> It would indicate users providing their own ->sk_data_ready() callback
>> must be responsible for waking up a kthread context blocked on
>> sock_recvmsg(..., MSG_WAITALL), when a second ->sk_data_ready() is
>> received before the first sock_recvmsg(..., MSG_WAITALL) completes.
>
> I agree, it looks like we need something like this?
> (not even build tested):
>
> 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;
> + conn->orig_data_ready(sk);
> return;
This allows iscsi login to work for me.
I ran it against the target-pending for-next branch.
Powered by blists - more mailing lists