linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pedro Fonseca <pfonseca@mpi-sws.org>
To: linux-fsdevel@vger.kernel.org
Cc: viro@zeniv.linux.org.uk, Theodore Ts'o <tytso@mit.edu>
Subject: Data races in generic_fillattr()
Date: Mon, 14 Apr 2014 20:24:32 +0200	[thread overview]
Message-ID: <534C27E0.9040401@mpi-sws.org> (raw)

Hi,

I've noticed that the function generic_fillattr() (fs/stat.c) in 
involved in multiple data races. Initially I reported this problem on 
the ext4 mailing list but it seems to be more general to the VFS layer.

Because of limited locking, when the inodes are updated and a stat() 
system call is concurrently executed, several 64-bit fields (e.g., 
atime, mtime, ctime, blocks) can potentially get incorrect values on 
32-bit architectures. In addition, it seems that it can also cause 
inconsistencies between the "blocks" field and the "size" field.

I would be glad if you could have a look at this problem and let me know 
if it's going to be fixed.

Thanks,
Pedro

             reply	other threads:[~2014-04-14 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 18:24 Pedro Fonseca [this message]
2014-04-24 11:55 ` Data races in generic_fillattr() Pedro Fonseca

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=534C27E0.9040401@mpi-sws.org \
    --to=pfonseca@mpi-sws.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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).