From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Török Edwin" <edwin@etorok.net>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Johannes Stezenbach <js@sig21.net>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: 4.7.0-rc7 ext4 error in dx_probe
Date: Mon, 8 Aug 2016 19:37:54 -0700 [thread overview]
Message-ID: <20160809023754.GG11291@birch.djwong.org> (raw)
In-Reply-To: <0bd292e7-818c-b708-4591-c7feec88f072@etorok.net>
On Tue, Aug 09, 2016 at 12:13:01AM +0300, Török Edwin wrote:
> On 2016-08-08 19:55, Darrick J. Wong wrote:
> > On Mon, Aug 08, 2016 at 12:08:18PM -0400, Theodore Ts'o wrote:
> >> On Sun, Aug 07, 2016 at 11:28:10PM -0700, Darrick J. Wong wrote:
> >>>
> >>> I have one lingering concern -- is it a bug that two processes could be
> >>> computing the checksum of a buffer simultaneously? I would have thought ext4
> >>> would serialize that kind of buffer_head access...
> >>
> >> Do we know how this is happening? We've always depended on the VFS to
> >> provide this exclusion. The only way we should be modifying the
> >> buffer_head at the same time if two CPU's are trying to modify the
> >> directory at the same time, and that should _never_ be happening, even
> >> with the new directory parallism code, unless the file system has
> >> given permission and intends to do its own fine-grained locking.
> >
> > It's a combination of two things, I think. The first is that the
> > checksum calculation routine (temporarily) set the checksum field to
> > zero during the computation, which of course is a no-no. The patch
> > fixes that problem and should go in.
>
> Thanks a lot for the patch.
> I wrote a small testcase (see below) that triggers the problem quite soon on
> my box with kernel 4.7.0, and seems to have survived so far with kernel
> 4.7.0+patch.
> When it failed it printed something like "readdir: Bad message".
>
> The drop caches part is quite important for triggering the bug, and might
> explain why this bug was hard to reproduce: IIUC this race condition can
> happen only if 2+ threads/processes try to access the same directory, and the
> directory's inode is not in the cache (i.e. was never cached, or got kicked
> out of the cache).
Could you formulate this into an xfstest, please? It would be very useful to
have this as a regression test.
(Or attach a Signed-off-by and I'll take care of it eventually.)
--D
>
>
> /*
> $ gcc trigger.c -o trigger -pthread
> $ ./trigger
> */
>
> #include <stdio.h>
> #include <sys/types.h>
> #include <sys/stat.h>
> #include <dirent.h>
> #include <string.h>
> #include <stdlib.h>
> #include <errno.h>
> #include <pthread.h>
> #include <unistd.h>
> #include <fcntl.h>
>
> #define FILES 100000
> #define THREADS 16
> #define LOOPS 1000
>
> static void die(const char *msg)
> {
> perror(msg);
> exit(EXIT_FAILURE);
> }
>
> static void* list(void* arg)
> {
> for(int i=0;i<LOOPS;i++) {
> DIR *d = opendir(".");
> if (!d) {
> die("opendir");
> }
> errno = 0;
> while(readdir(d)) {}
> if (errno) {
> die("readdir");
> }
> closedir(d);
> FILE *f = fopen("/proc/sys/vm/drop_caches", "w");
> if (f) {
> fputs("3", f);
> fclose(f);
> }
> }
> return NULL;
> }
>
> int main()
> {
> pthread_t t[THREADS];
>
> if(mkdir("ext4test", 0755) < 0 && errno != EEXIST)
> die("mkdir");
> if(chdir("ext4test") < 0)
> die("chdir");
> for (unsigned i=0;i < FILES;i++) {
> char name[16];
> snprintf(name, sizeof(name), "%d", i);
> int fd = open(name, O_WRONLY|O_CREAT, 0600);
> if (fd < 0)
> die("open");
> close(fd);
> }
> for (unsigned i=0;i < sizeof(t)/sizeof(t[0]); i++) {
> pthread_create(&t[i], NULL,list, NULL);
> }
> for (unsigned i=0;i < sizeof(t)/sizeof(t[0]); i++) {
> pthread_join(t[i], NULL);
> }
> return 0;
> }
>
>
>
> --
> Edwin Török | Co-founder and Lead Developer
>
> Skylable open-source object storage: reliable, fast, secure
> http://www.skylable.com
next prev parent reply other threads:[~2016-08-09 2:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 10:57 Johannes Stezenbach
2016-07-18 13:38 ` Theodore Ts'o
2016-07-18 14:17 ` Johannes Stezenbach
2016-07-27 11:58 ` Johannes Stezenbach
2016-08-03 14:50 ` Török Edwin
2016-08-05 10:35 ` Johannes Stezenbach
2016-08-05 17:02 ` Darrick J. Wong
2016-08-05 18:11 ` Johannes Stezenbach
2016-08-05 19:15 ` Darrick J. Wong
2016-08-08 3:56 ` Theodore Ts'o
2016-08-08 6:28 ` Darrick J. Wong
2016-08-08 16:08 ` Theodore Ts'o
2016-08-08 16:55 ` Darrick J. Wong
2016-08-08 21:13 ` Török Edwin
2016-08-09 2:37 ` Darrick J. Wong [this message]
2016-08-09 7:12 ` Török Edwin
2016-08-17 14:27 ` Török Edwin
2016-08-17 23:28 ` Darrick J. Wong
2016-08-22 7:33 ` Török Edwin
2016-09-01 16:40 ` Darrick J. Wong
2016-08-17 20:02 ` Johannes Stezenbach
2016-08-18 7:44 ` Török Edwin
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=20160809023754.GG11291@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=edwin@etorok.net \
--cc=js@sig21.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®