From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: memory corruption after "Fix race when checking i_size on direct i/o read"
Date: Sat, 8 Feb 2014 15:45:22 -0500 [thread overview]
Message-ID: <20140208204522.GG8801@fieldses.org> (raw)
I'm getting warnings about corruption of the kmalloc-32 slab on an nfs
server while running some regression tests.
A bisect lands on 9fe55eea7e4b444bafc42fa0000cc2d1d2847275 "Fix race
when checking i_size on direct i/o read". Is there any known problem
here?
It doesn't reproduce immediately and it's possible I could have made a
mistake on the bisect.
I'll verify and try to narrow down the reproducer.
--b.
next reply other threads:[~2014-02-08 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 20:45 J. Bruce Fields [this message]
2014-02-09 2:09 ` memory corruption after "Fix race when checking i_size on direct i/o read" J. Bruce Fields
2014-02-11 19:38 ` [PATCH] nfsd4: fix acl buffer overrun J. Bruce Fields
2014-02-11 20:25 ` Christoph Hellwig
2014-02-11 22:33 ` J. Bruce Fields
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=20140208204522.GG8801@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=swhiteho@redhat.com \
/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