Re: BUG in kcryptd?

On May 16 2007 17:52, Jan Engelhardt wrote:
>On May 16 2007 17:11, Udo van den Heuvel wrote:
>>
>>While opening an encrypted partition and trying to fsck it:
>
>Yeah, somewhere is a bug in it, I also get an oops with
>kcryptd in 2.6.20 on sparc64 after a few minutes (though,
>it's a NULL dereference there).

...which also seems to be gone for me with some 2.6.21.



	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • BUG in kcryptd?
    • From: Udo van den Heuvel <[email protected]>
  • Re: BUG in kcryptd?
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: Re: [PATCH] ieee1394: eth1394: bring back a parent device
• Next by Date: Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSM hook
• Previous by thread: Re: [dm-devel] Re: BUG in kcryptd?
• Next by thread: [PATCH] Make the scsi_wait_scan module only if SCSI_SCAN_ASYNC is enabled.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]