From: Linus Torvalds <torvalds@linux-foundation.org>
To: Bart Trojanowski <bart@jukie.net>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: vfat BKL/lock_super regression in v2.6.26-rc3-g8f59342
Date: Tue, 19 Aug 2008 17:11:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808191709130.3324@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20080820000339.GB28029@jukie.net>
On Tue, 19 Aug 2008, Bart Trojanowski wrote:
>
> Ok, I will test your patch and let you know in a few minutes.
Btw, while you're at it, can you try doing some random writes to that
thing, since the whole sync mount is quite possibly going to find a few
other cases like this.
IOW, _maybe_ you hit the only case that is ever going to be an issue for
sync mounts, and maybe you didn't. In my eternal quest to never actually
test anything myself, I'm hoping you can try some writing (and
over-writing) of files, since writes to the filesystem is where the whole
"sync" thing is going to show up (both metadata ie file creation and
removal, and "real" data ie normal write/truncate calls).
Linus
next prev parent reply other threads:[~2008-08-20 0:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 22:03 Bart Trojanowski
2008-08-19 22:06 ` [PATCH] make lock_super recursive to simulate BKL Bart Trojanowski
2008-08-19 22:21 ` Linus Torvalds
2008-08-20 1:14 ` Bart Trojanowski
2008-08-19 22:17 ` vfat BKL/lock_super regression in v2.6.26-rc3-g8f59342 Linus Torvalds
2008-08-20 0:03 ` Bart Trojanowski
2008-08-20 0:11 ` Linus Torvalds [this message]
2008-08-20 0:24 ` Bart Trojanowski
2008-08-20 0:18 ` Bart Trojanowski
2008-08-20 0:43 ` Linus Torvalds
2008-08-20 0:56 ` Linus Torvalds
2008-08-20 2:27 ` Bart Trojanowski
2008-08-20 21:23 ` Diego Calleja
2008-08-23 0:54 ` [PATCH] document additional vfat mount options Bart Trojanowski
2008-08-23 2:33 ` Grant Coady
2008-08-23 3:12 ` Bart Trojanowski
2008-08-23 3:14 ` Bart Trojanowski
2008-08-23 3:27 ` OGAWA Hirofumi
2008-08-23 13:11 ` Bart Trojanowski
2008-08-23 14:47 ` OGAWA Hirofumi
2008-08-23 3:10 ` OGAWA Hirofumi
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=alpine.LFD.1.10.0808191709130.3324@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=bart@jukie.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®