From: Andrew Morton <akpm@linux-foundation.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Chris Mason <clm@fb.com>, Michal Hocko <mhocko@suse.com>,
bugzilla-daemon@bugzilla.kernel.org,
bugzilla.kernel.org@plan9.de, linux-btrfs@vger.kernel.org,
linux-mm@kvack.org, Jan Kara <jack@suse.cz>
Subject: Re: [Bug 199931] New: systemd/rtorrent file data corruption when using echo 3 >/proc/sys/vm/drop_caches
Date: Tue, 5 Jun 2018 14:38:46 -0700 [thread overview]
Message-ID: <20180605143846.ec86323745ead25c74bc4c37@linux-foundation.org> (raw)
In-Reply-To: <34c7a73b-15d5-4d67-fa7c-0630b30a4c1c@i-love.sakura.ne.jp>
On Wed, 6 Jun 2018 06:22:25 +0900 Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> wrote:
> On 2018/06/06 5:03, Andrew Morton wrote:
> >
> > (switched to email. Please respond via emailed reply-to-all, not via the
> > bugzilla web interface).
> >
> > On Tue, 05 Jun 2018 18:01:36 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
> >
> >> https://bugzilla.kernel.org/show_bug.cgi?id=199931
> >>
> >> Bug ID: 199931
> >> Summary: systemd/rtorrent file data corruption when using echo
> >> 3 >/proc/sys/vm/drop_caches
> >
> > A long tale of woe here. Chris, do you think the pagecache corruption
> > is a general thing, or is it possible that btrfs is contributing?
>
> According to timestamp of my testcases, I was observing corrupted-bytes issue upon OOM-kill
> (without using btrfs) as of 2017 Aug 11. Thus, I don't think that this is specific to btrfs.
> But I can't find which patch fixed this issue.
That sounds different. Here, the corruption is caused by performing
drop_caches, not by an oom-killing.
next prev parent reply other threads:[~2018-06-05 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-199931-27@https.bugzilla.kernel.org/>
2018-06-05 20:03 ` Andrew Morton
2018-06-05 21:22 ` Tetsuo Handa
2018-06-05 21:38 ` Andrew Morton [this message]
2018-06-05 21:52 ` james harvey
2018-06-06 19:06 ` Marc Lehmann
2018-06-06 20:33 ` james harvey
2018-06-08 7:18 ` Duncan
2018-06-06 0:18 ` Chris Mason
2018-06-06 13:38 ` Liu Bo
2018-06-06 13:44 ` Chris Mason
2018-06-06 13:55 ` Liu Bo
2018-06-06 8:45 ` Michal Hocko
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=20180605143846.ec86323745ead25c74bc4c37@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=bugzilla.kernel.org@plan9.de \
--cc=clm@fb.com \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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