From: "Łukasz Fibinger" <lucke@o2.pl>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: RESVSP problems
Date: Fri, 25 May 2007 12:24:23 +0200 [thread overview]
Message-ID: <200705251224.23624.lucke@o2.pl> (raw)
In-Reply-To: <20070525050632.GG86004887@sgi.com>
On Friday 25 of May 2007, you wrote:
> On Thu, May 24, 2007 at 01:24:52PM +0200, Å?ukasz Fibinger wrote:
> > >>> You've probably hit:
> > >>> http://oss.sgi.com/bugzilla/show_bug.cgi?id=418
> > >>> unwritten extents remain unwritten after mmap() modifies them
> > >>>
> > >>> Bug dchinner about it... ;-)
> > >>
> > >> Dave, consider it a bugging from my humble self :-)
> > >
> > > Yeah, yeah ;)
> > >
> > > I'm waiting to see what happens with Nick's patches in .22 before
> > > going any further. If they are not merged into .22, then I think we
> > > should push the XFS specific fix in....
> >
> > I wonder, what's the status of it, Dave?
>
> A couple of days ago:
>
> http://marc.info/?l=linux-mm&m=117988295814519&w=2
>
I see. If that's the case, would sharing your 2.6.21 XFS specific fixes (you
have them, right?) with me be any problem for you?
Cheers,
Luke
next prev parent reply other threads:[~2007-05-25 10:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 11:24 RESVSP problems Łukasz Fibinger
2007-05-25 5:06 ` David Chinner
2007-05-25 10:24 ` Łukasz Fibinger [this message]
2007-05-25 11:24 ` David Chinner
2007-05-25 13:37 ` Łukasz Fibinger
2007-05-25 14:19 ` Christoph Hellwig
2007-05-28 0:50 ` David Chinner
-- strict thread matches above, loose matches on Subject: below --
2007-05-07 18:04 Łukasz Fibinger
2007-05-07 18:43 ` Eric Sandeen
2007-05-07 18:58 ` Łukasz Fibinger
2007-05-08 0:59 ` David Chinner
2007-05-08 5:03 ` Eric Sandeen
2007-05-08 5:25 ` 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=200705251224.23624.lucke@o2.pl \
--to=lucke@o2.pl \
--cc=dgc@sgi.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