From: Stan Hoeppner <stan@hardwarefreak.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [regression] stack overflow in xfs_buf_iodone_callbacks
Date: Thu, 21 Jun 2012 05:06:53 -0500 [thread overview]
Message-ID: <4FE2F23D.90303@hardwarefreak.com> (raw)
In-Reply-To: <20120621092104.GA3621@infradead.org>
On 6/21/2012 4:21 AM, Christoph Hellwig wrote:
> On Thu, Jun 21, 2012 at 07:18:03PM +1000, Dave Chinner wrote:
>> I don't have time to come up with a fix for this right now, but it
>> needs to be fixed before 3.5 releases. I don't have time because I'm
>> going to be AFK next week, so I'd appreciate it if someone could
>> look at fixing this in the mean time?
>
> I'll handle it.
Reading this exchange, seeing the teamwork, is really cool, and struck a
chord with me for some reason. Especially considering that "I'll handle
it" is probably a many hour (or day) commitment, made with 3 simple
words, at the drop of a hat.
Being part of a list where both deep technical development and 'simple'
end user issues are both handled, in a team fashion, is even cooler.
We probably don't say it enough, so I'll do so now.
Thank you guys, all the XFS developers, for the work you do that
benefits us all. And thanks to all my fellow XFS users, for helping
make this list what I think is a great community, and an example for
other lists to follow.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-06-21 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 9:18 [regression] stack overflow in xfs_buf_iodone_callbacks Dave Chinner
2012-06-21 9:21 ` Christoph Hellwig
2012-06-21 9:29 ` Dave Chinner
2012-06-21 10:06 ` Stan Hoeppner [this message]
2012-06-21 16:34 ` Christoph Hellwig
2012-06-21 23:24 ` Dave Chinner
2012-06-22 16:41 ` Christoph Hellwig
2012-06-22 23:39 ` Dave Chinner
2012-06-25 9:06 ` Christoph Hellwig
2012-06-26 2:20 ` Dave Chinner
2012-06-26 7:51 ` Christoph Hellwig
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=4FE2F23D.90303@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=hch@infradead.org \
--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