From: Lachlan McIlroy <lachlan@sgi.com>
To: Felix Blyakher <felixb@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 1/2] xfs: fix error handling in xfs_log_mount
Date: Wed, 11 Feb 2009 10:24:37 +1100 [thread overview]
Message-ID: <49920CB5.1020103@sgi.com> (raw)
In-Reply-To: <1E52072E-CA98-430B-9B2F-FDD0FDD1A7A4@sgi.com>
Felix Blyakher wrote:
>
> On Feb 10, 2009, at 1:57 PM, Christoph Hellwig wrote:
>
>> On Tue, Feb 10, 2009 at 01:56:31PM -0600, Felix Blyakher wrote:
>>> Isn't it a reworked Lachlan's patch:
>>>
>>> http://oss.sgi.com/archives/xfs/2009-02/msg00175.html
>>
>> The patch isn't related to that one at all,
>
> ... from the implementation point of view, yes.
>
>> but it aims to fix the
>> same issue.
>
> That's what I meant.
>
>> Should probably get a Reported-by: tag for him,
>
> Seems reasonable.
>
>> if
>> this is indeed the thing the original patch tried to fix.
>
> That was my understanding. Let's Lachlan pitch in.
I'd prefer both fixes go in so we have maximum defence against
this problem happening again but I'm really not fussed.
>
> Felix
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-02-10 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 19:44 [PATCH 0/2] 2.6.29 queue Christoph Hellwig
2009-02-10 19:44 ` [PATCH 1/2] xfs: fix error handling in xfs_log_mount Christoph Hellwig
2009-02-10 19:56 ` Felix Blyakher
2009-02-10 19:57 ` Christoph Hellwig
2009-02-10 20:09 ` Felix Blyakher
2009-02-10 23:24 ` Lachlan McIlroy [this message]
2009-02-11 22:39 ` Christoph Hellwig
2009-02-10 19:44 ` [PATCH 2/2] xfs: reject swapext ioctl on swapfiles Christoph Hellwig
2009-02-10 20:00 ` Felix Blyakher
2009-02-12 19:19 ` [PATCH 0/2] 2.6.29 queue 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=49920CB5.1020103@sgi.com \
--to=lachlan@sgi.com \
--cc=felixb@sgi.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 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.