All of
 help / color / mirror / Atom feed
From: Matthew Wilcox <>
Subject: Re: Whatever happened to write_super_lockfs?
Date: Fri, 18 Jul 2003 22:09:52 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Jul 18, 2003 at 02:06:51PM -0700, Andreas Dilger wrote:
> No.  I've been trying to get Chris Mason to submit the (very small) code
> into the kernel for a long time now.  It is needed for LVM and EVMS snapshots.
> The inclusion is being slowed down by the lack of Viro.

Can we see the patch so I can document the locking?

"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  reply	other threads:[~2003-07-18 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 20:39 Whatever happened to write_super_lockfs? Matthew Wilcox
2003-07-18 21:06 ` Andreas Dilger
2003-07-18 21:09   ` Matthew Wilcox [this message]
2003-07-18 21:28     ` Andreas Dilger

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.