Description of problem:
A client uses racoon.conf for IPSEC and it will give kernel panic when
it is being used.

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. racoon.conf has been set as following;

remote anonymous 
{ 
exchange_mode main; 
doi ipsec_doi; 
situation identity_only; 
initial_contact off; 
passive on; 
proposal_check obey; 
generate_policy on; 
proposal { 
encryption_algorithm 3des; 
hash_algorithm sha1; 
authentication_method pre_shared_key; 
dh_group 2; 
} 
} 

Actual results:
Kernel Dumps

Expected results:
IPSEC should work

Additional info:

necessary information has been attached in a zip file.

One of the trace call shows following;
Call Trace:   [<c0280e85>] xfrm_policy_gc_kill [kernel] 0x45 (0xf7fa7f50)
[<c012ee9a>] __run_task_queue [kernel] 0x6a (0xf7fa7f74)
[<c013acfd>] context_thread [kernel] 0x13d (0xf7fa7f8c)

The other one follows;
Call Trace:   [<c028092b>] xfrm_policy_gc_task [kernel] 0xbb (0xc46d5f5c)
[<c013ae2d>] context_thread [kernel] 0x13d (0xc46d5f8c)
[<c013acf0>] context_thread [kernel] 0x0 (0xc46d5fe0)
[<c010958d>] kernel_thread_helper [kernel] 0x5 (0xc46d5ff0)


It seems that it is panicing at the same place.