linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 89131] Hangs when checking torrent through libtorrent; kernel BUG at mm/iov_iter.c:219!
Date: Mon, 19 Jan 2015 17:36:59 +0000	[thread overview]
Message-ID: <bug-89131-13602-guFosNZOf7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-89131-13602@https.bugzilla.kernel.org/>

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

--- Comment #11 from Theodore Tso <tytso@mit.edu> ---
Created attachment 163831
  --> https://bugzilla.kernel.org/attachment.cgi?id=163831&action=edit
debugging patch (should apply for 3.17 and 3.18)

This BUG_ON is happening from the mm part of the direct_io code, which is
supposed to be file system independent, and so I don't know that half of the
DIO code as well.   Can you try applying the attached patch to see if it gets
us any useful information when the bug triggers?

Also, at this point it would be *really* useful if we could get a reproduction
case that doesn't require using rtorrent -- i.e., something that uses just dd,
or maybe a simple C program.   Would it be possible to run the a tty-mode
torrent on a serial console under strace, or some such, so we can get figure
out what the system calls were that apparently triggered the BUG_ON?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2015-01-19 17:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 13:19 [Bug 89131] New: Hangs when checking torrent through libtorrent; kernel BUG at mm/iov_iter.c:219! bugzilla-daemon
2014-12-17  9:49 ` [Bug 89131] " bugzilla-daemon
2014-12-17 11:08 ` bugzilla-daemon
2014-12-17 11:20 ` bugzilla-daemon
2014-12-17 11:36 ` bugzilla-daemon
2014-12-18  9:49 ` bugzilla-daemon
2014-12-19 16:02 ` bugzilla-daemon
2014-12-19 16:30 ` bugzilla-daemon
2014-12-19 16:37 ` bugzilla-daemon
2014-12-19 16:37 ` bugzilla-daemon
2015-01-19  7:54 ` bugzilla-daemon
2015-01-19 17:36 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-89131-13602-guFosNZOf7@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).