[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFL455kEoLQF+vc2MGmtLdrQ-=U+HJzqgknZmM54iCPJD1p_mA@mail.gmail.com>
Date: Mon, 13 Feb 2023 12:59:07 +0100
From: Maurizio Lombardi <mlombard@...hat.com>
To: David Jeffery <djeffery@...hat.com>
Cc: target-devel@...r.kernel.org,
"Martin K . Petersen" <martin.petersen@...cle.com>,
Mike Christie <michael.christie@...cle.com>,
Laurence Oberman <loberman@...hat.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scsi: target: iscsi: set memalloc_noio with loopback
network connections
st 8. 2. 2023 v 21:10 odesÃlatel David Jeffery <djeffery@...hat.com> napsal:
>
>
> + /*
> + * If the iscsi connection is over a loopback device from using
> + * iscsi and iscsit on the same system, we need to set memalloc_noio to
> + * prevent memory allocation deadlocks between target and initiator.
> + */
> + rcu_read_lock();
> + dst = rcu_dereference(conn->sock->sk->sk_dst_cache);
> + if (dst && dst->dev && dst->dev->flags & IFF_LOOPBACK)
> + loopback = true;
> + rcu_read_unlock();
Hi Mike,
I tested it, it works. The customer also confirmed that it fixes the
deadlock on his setup.
Maurizio
Powered by blists - more mailing lists