From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: sync_blockdev in xfs_flush_device_work
Date: Sat, 29 Sep 2007 13:09:21 +0200 [thread overview]
Message-ID: <20070929110921.GA2466@lst.de> (raw)
How is the sync_blockdev in the ENOSP path going to help it? It only
syncs the block device mapping which XFS doesn't use it at all.
next reply other threads:[~2007-09-29 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 11:09 Christoph Hellwig [this message]
2007-10-02 23:23 ` sync_blockdev in xfs_flush_device_work David Chinner
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=20070929110921.GA2466@lst.de \
--to=hch@lst.de \
--cc=xfs@oss.sgi.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 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.