From: Fan Du <fan.du@windriver.com>
Subject: Why care about signal when instantiate an crypt template
Date: Fri, 11 Apr 2014 15:37:53 +0800
Message-ID: <53479BD1.3050508@windriver.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
	format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
To: <linux-crypto@vger.kernel.org>
Sender: linux-crypto-owner@vger.kernel.org

Hi,

I recently bump into a issue, ike daemon got interrupted(EINTR),
after looking at the code, it seems there are places in crypto code
where returning EINTR when current tasks has signal pending.

=46or example:
crypto_alloc_base and crypto_alloc_tfm

435 err:
436                 if (err !=3D -EAGAIN)
437                         break;
438                 if (signal_pending(current)) {
439                         err =3D -EINTR;
440                         break;
441                 }
442         }

I can't understand why the codes here needs to care about signals?

Thanks a lot for any explanations.

--=20
=E6=B5=AE=E6=B2=89=E9=9A=8F=E6=B5=AA=E5=8F=AA=E8=AE=B0=E4=BB=8A=E6=9C=9D=
=E7=AC=91

--fan