linux-ext4 - [Bug 19212] kernel BUG at /build/buildd/linux-2.6.32/fs/ext4/extents.c:1716

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: <201106261220.p5QCKKW5029435@demeter2.kernel.org>
Date:	Sun, 26 Jun 2011 12:20:20 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 19212] kernel BUG at
 /build/buildd/linux-2.6.32/fs/ext4/extents.c:1716

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


Mikhail Vorozhtsov <mikhail.vorozhtsov@...il.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mikhail.vorozhtsov@...il.co
                   |                            |m




--- Comment #1 from Mikhail Vorozhtsov <mikhail.vorozhtsov@...il.com>  2011-06-26 12:20:18 ---
Seems like it hit me. A few days ago a regular fsck run detected
multiply-claimed blocks on my /home and asked me to clone them. I answered
"yes". After that my kernel started oopsing 3-4 times a day. The process is
either transmission-gtk or flush-XYZ (with slightly different call traces, but
with the same code location). The message is (transmission-gtk variant, the
exact message is not in the logs, I'm posting the lines I wrote down on a
paper):

kernel BUG at fs/ext4/extents.c:1784
RIP: ext4_ext_insert_extent
Call trace:
  ext4_ext_map_blocks
? pagevec_lookup_tag
  ext4_map_blocks
  mpage_da_map_and_submit
? jbd2_journal_start
? ext4_da_writepages
  __filemap_fdatawrite_range
  filemap_write_and_wait_range
  vfs_fsync_range
  vfs_fsync
  sys_fsync
  system_call_fastpath

After rebooting fsck -f doesn't find any errors.

Kernel version is 2.6.39.1, e2fsprogs version is 1.41.14.

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