public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jindrich Makovicka <makovick@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.39-rc1 data corruption with rtorrent
Date: Sat, 2 Apr 2011 22:21:18 +0200	[thread overview]
Message-ID: <20110402222118.3b5c2fa8@holly> (raw)

[-- Attachment #1: Type: text/plain, Size: 519 bytes --]

Hi,

I hit an rtorrent data corruption issue again. But this time, rtorrent
seems to write data that were mmapped by other processes (in the
downloaded files, I found my data from Chromium and later the data
produced by the testing utility by Linus from
http://lkml.org/lkml/2006/12/27/180). Unfortunately, I was so far
unable to reproduce the issue just with the testing utility.

I reverted to stable 2.6.38.2 for now as I don't feel like broadcasting
my private data via bittorrent.

Regards,
-- 
Jindrich Makovicka

[-- Attachment #2: config-2.6.39-rc1.gz --]
[-- Type: application/x-gzip, Size: 18230 bytes --]

             reply	other threads:[~2011-04-02 20:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02 20:21 Jindrich Makovicka [this message]
2011-04-03  0:08 ` 2.6.39-rc1 data corruption with rtorrent Anca Emanuel

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=20110402222118.3b5c2fa8@holly \
    --to=makovick@gmail.com \
    --cc=linux-kernel@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