From: Craig Milo Rogers <rogers@ISI.EDU>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrew Morton <akpm@zip.com.au>, Chris Mason <mason@suse.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 12/16] fix race between writeback and unlink
Date: Tue, 04 Jun 2002 15:05:03 -0700 [thread overview]
Message-ID: <8692.1023228303@ISI.EDU> (raw)
In-Reply-To: Your message of "Tue, 04 Jun 2002 13:23:04 PDT." <Pine.LNX.4.44.0206041320280.29100-100000@home.transmeta.com>
>Sure. However, I don't think it should come as any surprise to anybody
>that trying to write to two different points in the same file is a bad
>idea.
Databases?
Craig Milo Rogers
next prev parent reply other threads:[~2002-06-04 22:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 8:43 [patch 12/16] fix race between writeback and unlink Andrew Morton
2002-06-01 16:42 ` Linus Torvalds
2002-06-01 19:19 ` Andrew Morton
2002-06-01 20:04 ` William Lee Irwin III
2002-06-01 22:25 ` Andrew Morton
2002-06-03 4:27 ` [RFC] iput() cleanup (was Re: [patch 12/16] fix race between writeback and unlink) Linus Torvalds
2002-06-03 16:26 ` Andreas Dilger
2002-06-03 16:47 ` Linus Torvalds
2002-06-03 19:09 ` Chris Mason
2002-06-03 19:34 ` Linus Torvalds
2002-06-03 19:49 ` Chris Mason
2002-06-03 19:55 ` Linus Torvalds
2002-06-03 22:10 ` [patch 12/16] fix race between writeback and unlink Chris Mason
2002-06-03 22:19 ` Linus Torvalds
2002-06-03 22:30 ` Andrew Morton
2002-06-04 18:47 ` Linus Torvalds
2002-06-04 20:15 ` Andrew Morton
2002-06-04 20:23 ` Linus Torvalds
2002-06-04 20:40 ` Andrew Morton
2002-06-04 21:37 ` Linus Torvalds
2002-06-04 22:04 ` Benjamin LaHaise
2002-06-04 22:08 ` Andrew Morton
2002-07-07 20:38 ` Riley Williams
2002-06-04 22:05 ` Craig Milo Rogers [this message]
2002-06-04 22:08 ` Linus Torvalds
2002-06-03 22:36 ` Chris Mason
2002-06-03 22:47 ` Andrew Morton
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=8692.1023228303@ISI.EDU \
--to=rogers@isi.edu \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=torvalds@transmeta.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