From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: mpatocka@redhat.com
Subject: Re: [PATCH 0/5] [XFS] Spurious ENOSPC fixes
Date: Sun, 15 Mar 2009 22:11:49 +1100 [thread overview]
Message-ID: <20090315111149.GX26138@disturbed> (raw)
In-Reply-To: <1237114679-18808-1-git-send-email-david@fromorbit.com>
On Sun, Mar 15, 2009 at 09:57:54PM +1100, Dave Chinner wrote:
> This series fix the spurious ENOSPC problems reported by and
> partially solved by Mikulas Patocka. This series makes the recently
> posted QA tests 203 and 204 pass.
>
> Mikulas, if I've got any of the attributions wrong for the
> bits of your code I used, let me know and I'll fix them.
I'm about to resend these with the correct sign-off
(i.e. david@fromorbit.com). Please ignore all the patches
with a different signed-off by.
[ I screwed up the .gitconfig earlier today when setting up a
new build/test box and didn't notice that the local commits
in the kernel tree had the wrong address... ]
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-03-15 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 10:57 [PATCH 0/5] [XFS] Spurious ENOSPC fixes Dave Chinner
2009-03-15 10:57 ` [PATCH 1/5] [XFS] Use xfs_sync_inodes() for device flushing Dave Chinner
2009-03-17 13:08 ` Mikulas Patocka
2009-03-18 4:17 ` Dave Chinner
2009-03-18 16:14 ` Mikulas Patocka
2009-03-20 4:30 ` Dave Chinner
2009-03-25 15:19 ` Mikulas Patocka
2009-03-15 10:57 ` [PATCH 2/5] [XFS] Make inode flush at ENOSPC synchronous Dave Chinner
2009-03-15 10:57 ` [PATCH 3/5] [XFS] Block callers of xfs_flush_inodes() correctly Dave Chinner
2009-03-15 10:57 ` [PATCH 4/5] [XFS] Flush delayed allcoation blocks on ENOSPC in create Dave Chinner
2009-03-15 10:57 ` [PATCH 5/5] [XFS] Remove xfs_flush_space Dave Chinner
2009-03-15 11:11 ` Dave Chinner [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=20090315111149.GX26138@disturbed \
--to=david@fromorbit.com \
--cc=mpatocka@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox