Why care about signal when instantiate an crypt template

[Fan Du <fan.du@windriver.com>]

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.

For example:
crypto_alloc_base and crypto_alloc_tfm

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

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

Thanks a lot for any explanations.

-- 
浮沉随浪只记今朝笑

--fan