| 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: <20121022044252.GE4768@thunk.org> Date: Mon, 22 Oct 2012 00:42:52 -0400 From: Theodore Ts'o <tytso@....edu> To: Volodymyr Mieshkov <volodymyr.mieshkov@...com> Cc: linux-ext4@...r.kernel.org Subject: Re: The patch at 'patchwork.ozlabs.org/patch/192079' On Thu, Oct 18, 2012 at 02:02:33PM +0300, Volodymyr Mieshkov wrote: > Hi, > > My name is Volodymyr. Sorry, I don't know your name, but I'd like to > ask you about some issue. > Recently I got an Linux kernel panic on my system and submitted the > patch to prevent it here: http://patchwork.ozlabs.org/patch/192079/. > Before that I found at one of the forum a thread that described a > similar problem, > and you suggested the patch to fix it: > http://www.gossamer-threads.com/lists/linux/kernel/1326686. > I used your idea, and I would like to re-submit the path with your > authorship. > Sorry, I must ask you before I've submitted the patch. I don't want > to break your authorship. Hi Volodymyr, The patch which I suggested in the thread which you referenced was intended to debug the bug to find the real root cause of the issue. If in fact the WARN() is triggering on your 3.0 system, then there's a bug that we should be trying to fix. Instead of using this patch to paper over the problem, I'd much rather see if we can figure out why jinode was NULL in the first place. Can you reliably reproduce this failure? Regards, - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists