linux-ext4 - [Bug 42895] jbd2 makes all system unresponsive

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: <20120515145440.C99DC11FCF0@bugzilla.kernel.org>
Date:	Tue, 15 May 2012 14:54:40 +0000 (UTC)
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 42895] jbd2 makes all system unresponsive

https://bugzilla.kernel.org/show_bug.cgi?id=42895





--- Comment #12 from Jan Kara <jack@...e.cz>  2012-05-15 14:54:40 ---
(In reply to comment #11)
> Enabling ext4_mark_inode_dirty gives me constant flood of events where
> xfce4-terminal dirties mostly two same inodes:
> http://paste.ubuntu.com/988896/
> Is it expected behavior? This is default terminal in Xubuntu.
  Yeah, forgot about it. Sorry for extra work. Terminal writes to some pipe
inode or socket when it outputs to the screen... Just create tmpfs if you don't
have one (e.g. mkdir /tmp/mem; mount -t tmpfs none /tmp/mem/) and then gather
the output like "cat /sys/kernel/debug/tracing/trace_pipe
>/tmp/mem/dirty_trace".

BTW writing to sockets or named pipes is often source of filesystem
modifications because mtime of those inodes change - e.g. postfix is causing
these relatively frequently, xfce4-terminal is another such case. It's a bit
tricky to avoid these because I'd be recluctant to completely stop updating
mtime on socket/pipe inodes as some strange tool may rely on that. But I've got
some idea which may work so if this is indeed the problem, I can look at it
again.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
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