From: Boaz Harrosh <bharrosh@panasas.com>
To: Idan Kedar <idank@tonian.com>
Cc: <linux-fsdevel@vger.kernel.org>, <osd-dev@open-osd.org>,
<solo@tonian.com>, <bhalevy@tonian.com>, <ilya@tonian.com>
Subject: Re: [PATCH] exofs: clean up the correct page collection on write error
Date: Sun, 2 Dec 2012 14:58:30 +0200 [thread overview]
Message-ID: <50BB5076.3000703@panasas.com> (raw)
In-Reply-To: <CABpMAy+=3CP1nQ4m27xKjLnpn6dzvspW3WmfSjEJooLCqY8sdg@mail.gmail.com>
On 12/02/2012 11:57 AM, Idan Kedar wrote:
> On Fri, Nov 30, 2012 at 4:10 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
<>
>> err:
>> - _unlock_pcol_pages(pcol, ret, WRITE);
>> - pcol_free(pcol);
>> + if (!pcol_copy) /* Failed before ownership transfer */
>> + pcol_copy = pcol;
>> + _unlock_pcol_pages(pcol_copy, ret, WRITE);
>> + pcol_free(pcol_copy);
>> kfree(pcol_copy);
>>
>> return ret;
>> --
>> 1.7.10.2.677.gb6bc67f
>>
>
> I started with that implementation, but it seemed less readable to me.
>
I don't mind the readability, it is not that bad. But I do mind the extra
local variable I'd rather not have it. (I hate it when two places have the
same info, they get out of sync fast, I'd rather do with one)
> On Fri, Nov 30, 2012 at 4:15 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
>> On 11/30/2012 04:10 PM, Boaz Harrosh wrote:
>>
>> I forgot to ask do you need this for stable?
>>
>> Boaz
>
> nope.
>
Thanks
Boaz
prev parent reply other threads:[~2012-12-02 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 14:49 [PATCH] exofs: clean up the correct page collection on write error Idan Kedar
2012-11-30 14:10 ` Boaz Harrosh
2012-11-30 14:15 ` Boaz Harrosh
2012-11-30 14:26 ` [PATCH] exofs: don't leak io_state and pages on read error Boaz Harrosh
2012-11-30 14:28 ` [PATCH] exofs: Remove dead code in read_exec Boaz Harrosh
2012-12-02 9:57 ` [PATCH] exofs: clean up the correct page collection on write error Idan Kedar
2012-12-02 12:58 ` Boaz Harrosh [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=50BB5076.3000703@panasas.com \
--to=bharrosh@panasas.com \
--cc=bhalevy@tonian.com \
--cc=idank@tonian.com \
--cc=ilya@tonian.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=solo@tonian.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;
as well as URLs for NNTP newsgroup(s).