linux-ext4 - [Bug 89131] Hangs when checking torrent through libtorrent; kernel BUG at mm/iov

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 for Android: free password hash cracker in your pocket

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

Message-ID: <bug-89131-13602-UR7rds3Sef@https.bugzilla.kernel.org/>
Date:	Fri, 19 Dec 2014 16:02:38 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 89131] Hangs when checking torrent through libtorrent; kernel
 BUG at mm/iov_iter.c:219!

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

Theodore Tso <tytso@....edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@....edu

--- Comment #6 from Theodore Tso <tytso@....edu> ---
Couple of questions.   First of all, is there any chance you could give a try
with 3.18.0, and see if it fails there?

Also, can you try to get line numbers out of the stack dump?   

Also, how long does it take before you trigger the failure?  I'm in particular
interested in seeing where this comes from:

[ 4244.680376]  [<ffffffff81203313>] __blockdev_direct_IO+0x25e3/0x3630

Part of the problem here is that fs/direct_io.c has a bunch of inline
functions, so it becomes tricky to figure out where the call to advance_iovec
comes from.   This looks like a bug in the core direct I/O code, but we do a
fair amount of regression testing and this is a new one; it's a bit surprising
no once else found this when running xfstests.

To get the line numbers, compile the kernel with

CONFIG_DEBUG_INFO=y

(You can also set CONFIG_DEBUG_INFO_REDUCED to reduce the size of your kernel
build.)

Then use the addr2line program to translate the address to a line number, i.e.:

addr2line -e /path/to/kernel/build/vmlinux -i -a ffffffff81203313

Finally, can you send me an output of dumpe2fs -h of your ext3/ext4 file
system, just so I can understand what file system features are enabled with
your file system.

Thanks!!

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