[IPCOMP]: Fix false smp_processor_id warning

This patch fixes a false-positive from debug_smp_processor_id().

The processor ID is only used to look up crypto_tfm objects.
Any processor ID is acceptable here as long as it is one that is
iterated on by for_each_cpu().

Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>

authored by Herbert Xu and committed by David S. Miller 6fc8b9e7 cb94c62c

+2 -2
+1 -1
net/ipv4/ipcomp.c
··· 358 358 int cpu; 359 359 360 360 /* This can be any valid CPU ID so we don't need locking. */ 361 - cpu = smp_processor_id(); 361 + cpu = raw_smp_processor_id(); 362 362 363 363 list_for_each_entry(pos, &ipcomp_tfms_list, list) { 364 364 struct crypto_tfm *tfm;
+1 -1
net/ipv6/ipcomp6.c
··· 354 354 int cpu; 355 355 356 356 /* This can be any valid CPU ID so we don't need locking. */ 357 - cpu = smp_processor_id(); 357 + cpu = raw_smp_processor_id(); 358 358 359 359 list_for_each_entry(pos, &ipcomp6_tfms_list, list) { 360 360 struct crypto_tfm *tfm;