Re: NULL pointer at kset_find_obj

[David Howells <dhowells@redhat.com>]

CAI Qian <caiqian@redhat.com> 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 that you encountered the key-not-yet-valid problem
> > due to your h/w clock showing a value prior to the start date on the key.
> Hmm, unsure about how to check it, but here is the full log prior the panic,
> http://people.redhat.com/qcai/stable/log.key

This bit here:

    [    2.693861] Loading module verification certificates 
    [    2.698920] X.509: Cert 8b7774b08bc4ee9637073434c10f0823f6fbe523 is not yet valid 
    [    2.706444] MODSIGN: Problem loading in-kernel X.509 certificate (-129) 

After those lines, you have indeed managed to load some modules:

    [   35.218540] Modules linked in: kvm(F+) microcode(F+) i2c_nforce2(F) edac_core(F) k8temp(F) shpchp(F) serio_raw(F) pcspkr(F) xfs(F) libcrc32c(F) sd_mod(F) crc_t10dif(F) sr_mod(F) cdrom(F) mptsas(F) radeon(F) i2c_algo_bit(F) scsi_transport_sas(F) drm_kms_helper(F) mptscsih(F) ttm(F) drm(F) mptbase(F) i2c_core(F) usb_storage(F) dm_mirror(F) dm_region_hash(F) dm_log(F) dm_mod(F) 

Each of which appears to have incurred the:

    [   34.917174] Request for unknown module key 'Magrathea: Glacier signing key: 8b7774b08bc4ee9637073434c10f0823f6fbe523' err -11 

error.

So that seems to be what I thought it was, but it doesn't seem to have been a
problem for most modules.

David