David Howells writes:
> Btw, one thing I've noticed is that sysfs appears to be able to execute code
> in the module by way of parameter alterations before the module is completely
> set up.
It's preceeded by the module parameter parsing, which can do the same
thing, so I don't think it's an issu
Rusty Russell wrote:
> > I think this bit should be waved in front of Rusty. It looks like it
> > might be a bug in error handling code.
>
> It does look like it, but I can't see it. The module code doesn't see
> an error (presumably sig_enforce is false), so we continue processing
> the modul
CAI Qian wrote:
> > Can you check back earlier in the dmesg to see whether the kernel tried to
> > load the key? -11 is presumably -EAGAIN - in which case no such key was
> > found
> > (rather than there being a cached lookup failure which is what -ENOKEY would
> > indicate). It is possible tha
David Howells writes:
> CAI Qian wrote:
>
>> Just booted the latest mainline,
>>
>> [ 35.217698] Request for unknown module key 'Magrathea: Glacier signing
>> key: 8b7774b08bc4ee9637073434c10f0823f6fbe523' err -11
>
> Can you check back earlier in the dmesg to see whether the kernel tried to
>
- Original Message -
> From: "David Howells"
> To: "CAI Qian" , ru...@rustcorp.com.au
> Cc: dhowe...@redhat.com, "LKML"
> Sent: Wednesday, April 3, 2013 1:38:50 AM
> Subject: Re: NULL pointer at kset_find_obj
>
> CAI
CAI Qian wrote:
> Just booted the latest mainline,
>
> [ 35.217698] Request for unknown module key 'Magrathea: Glacier signing
> key: 8b7774b08bc4ee9637073434c10f0823f6fbe523' err -11
Can you check back earlier in the dmesg to see whether the kernel tried to
load the key? -11 is presumably -
Just booted the latest mainline,
[ 35.217698] Request for unknown module key 'Magrathea: Glacier signing key:
8b7774b08bc4ee9637073434c10f0823f6fbe523' err -11
[ 35.218511] BUG: unable to handle kernel paging request at a03093f0
[ 35.218521] IP: [] kset_find_obj+0x30/0x80
[ 35.
7 matches
Mail list logo