linux-kernel - Re: ext3 issue on 3.6.1

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1350596425.1366.15.camel@x61.thuisdomein>
Date:	Thu, 18 Oct 2012 23:40:25 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Jan Kara <jack@...e.cz>
Cc:	Fabio Coatti <fabio.coatti@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: ext3 issue on 3.6.1

On Thu, 2012-10-18 at 23:23 +0200, Jan Kara wrote:
> On Fri 12-10-12 14:57:55, Fabio Coatti wrote:
> > [13031.051521] ------------[ cut here ]------------
> > [13031.051576] WARNING: at fs/inode.c:280 drop_nlink+0x1b/0x35()
> > [13031.051624] Hardware name: ProLiant BL465c G7
> > [13031.051668] Pid: 3344, comm: php Tainted: G        W
> > 3.6.1-1000hz-preempt #2
> > [13031.051746] Call Trace:
> > [13031.051787]  [<ffffffff810578c4>] ? warn_slowpath_common+0x73/0x87
> > [13031.051837]  [<ffffffff810ec628>] ? drop_nlink+0x1b/0x35
> > [13031.051885]  [<ffffffff8118ad51>] ? nfs_dentry_iput+0x33/0x49
> > [13031.051934]  [<ffffffff810ea920>] ? d_kill+0xe8/0x108
> > [13031.051980]  [<ffffffff810eb001>] ? dput+0x147/0x154
> > [13031.052027]  [<ffffffff810d9e46>] ? __fput+0x19a/0x1b2
> > [13031.052073]  [<ffffffff8106bdf0>] ? task_work_run+0x4c/0x60
> > [13031.052123]  [<ffffffff815ff5e8>] ? int_signal+0x12/0x17
> > [13031.052169] ---[ end trace e60232a455c8e2dd ]---
>   And this seems unrelated - likely an NFS problem... Let's sort this out
> if you still see it after ext3 issue is solved.

Looks rather similar too https://lkml.org/lkml/2012/8/29/165 , doesn't
it?


Paul Bolle

--
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/