| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20080508190554.GB4090@atrey.karlin.mff.cuni.cz> Date: Thu, 8 May 2008 21:05:54 +0200 From: Jan Kara <jack@...e.cz> To: Yan Seiner <yan@...ner.com> Cc: linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: Kenrel oops > > Jan Kara > >> I just had this kernel oops. Approximately 5 mintes later, the machine > >> hard-locked. Can anyone give me some guidance on where to look? > > Any chance of reproducing this without the NVidia module? It looks > > like filp->f_op->flush contained an invalid pointer (although > > ffff81007e3d1300 doesn't look completely insane but more like a pointer > > to data than to a function). Weren't you playing with rmmod before this > > happened? > > I was playing with Xephyr on top of X, so it's possible that the script I > was using tried to load the opensource nv module on top of the nvidia > module and/or that there was repeated insmod/rmmod of nvidia and nv before > this happened. I mean more like removing some filesystem modules or so which doesn't seem to be the case. > I've not been able to reproduce this since. OK. So far I have no clue what could have caused this (besides some weird corruption with nvidia module) so I'll wait if someone comes with a similar report... Honza -- Jan Kara <jack@...e.cz> SuSE CR Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists