From: Jarek Poplawski <jarkao2@o2.pl>
To: Neil Brown <neilb@suse.de>
Cc: David Chinner <dgc@sgi.com>, lkml <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Race between generic_forget_inode() and sync_sb_inodes()?
Date: Fri, 30 Nov 2007 10:41:48 +0100 [thread overview]
Message-ID: <20071130094148.GB2017@ff.dom.local> (raw)
In-Reply-To: <18255.17747.484721.210728@notabene.brown>
On 30-11-2007 00:03, Neil Brown wrote:
> On Friday November 30, dgc@sgi.com wrote:
...
>> Or have I just not had enough coffee this morning?
>
> :-) And I cannot even blame the lack of coffee as I don't drink it.
>
Looks like logical error...
(Or I haven't had enough coffee this morning either?)
Regards,
Jarek P.
prev parent reply other threads:[~2007-11-30 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 21:55 Race between generic_forget_inode() and sync_sb_inodes()? David Chinner
2007-11-29 22:07 ` Neil Brown
2007-11-29 22:24 ` David Chinner
2007-11-29 23:03 ` Neil Brown
2007-11-30 9:41 ` Jarek Poplawski [this message]
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=20071130094148.GB2017@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.