| 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: <20111017090847.GO30887@longonot.mountain> Date: Mon, 17 Oct 2011 12:08:47 +0300 From: Dan Carpenter <dan.carpenter@...cle.com> To: Tao Ma <tm@....ma> Cc: linux-ext4@...r.kernel.org Subject: Re: corruption on 3.1.0-rc9-next-20111011+ On Mon, Oct 17, 2011 at 04:51:09PM +0800, Tao Ma wrote: > Hi Dan, > On 10/17/2011 04:10 PM, Dan Carpenter wrote: > > On Mon, Oct 17, 2011 at 09:57:00AM +0300, Dan Carpenter wrote: > >> Hi list, > >> > >> I hit a sanity check in ext4_ext_insert_index() and my filesystem > >> went read only. > >> > > > > Hm... That's odd. My netbook hit the same bug last night as well. > > It's running the same kernel version and config but compiled on a > > different system. I don't know why it has the '+' char on the end of > > the version name. Maybe it always does that for linux-next, because > > I don't have any patches applied. > > > > I've left it with the readonly filesystem for now. > This is caused by the commit 4fd30c033. Sorry for the trouble and please > check the patch I just sent. It should resolve the warning. > Thanks. I don't have a way to reproduce the bug. Once I get a system fixed enough to install a new kernel, the problem has gone away. I've was running the old kernel for days before seeing the issue. regards, dan carpenter -- 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