From: "Krzysztof Błaszkowski" <kb@sysmikro.com.pl>
To: Christoph Hellwig <hch@infradead.org>
Cc: Carlos Maiolino <cmaiolino@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: Re: freevxfs: hp-ux support. patchset 1-7/7 rev 2
Date: Wed, 01 Jun 2016 11:23:32 +0200 [thread overview]
Message-ID: <1464773012.900.105.camel@linux-q3cb.site> (raw)
In-Reply-To: <20160601073310.GA6787@infradead.org>
Hi Christoph,
On Wed, 2016-06-01 at 00:33 -0700, Christoph Hellwig wrote:
> Yeah, this was just getting started. I've spent some more time on the
> whole inode issues and have implemented this a bit different from what
> you did, although the end result is very similar. Can you take a look
> at the tree here:
>
> http://git.infradead.org/users/hch/vfs.git/shortlog/refs/heads/freevxfs
>
> > Do you think other patches should be updated with regard to the patch
> > you sent ?
>
> Please take a look at the branch above.
I think that there are no "kfree(pfp); kfree(sfp); return 0;" in
vxfs_read_fshead() still. Are pfp and sfp needed anywhere ? I am sure
they are not so there is a memory leak without these kfrees every mount.
I am not sure absolutely of that read_fshead() is missing these kfrees
because I have seen just these diffs, anyway I did not notice "+kfree".
so .. whose patch is more accurate ?
needles to say that I prefer to have limited scope of visibility of
inode_cachep to the inode.c only.
Thanks,
--
Krzysztof Blaszkowski
next prev parent reply other threads:[~2016-06-01 9:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 14:45 freevxfs: hp-ux support. patchset 1-7/7 Krzysztof Błaszkowski
2016-05-26 15:43 ` freevxfs: hp-ux support. (working) " Krzysztof Błaszkowski
2016-05-26 15:53 ` r Christoph Hellwig
2016-05-26 17:44 ` r Krzysztof Błaszkowski
2016-05-28 19:40 ` freevxfs: hp-ux support. patchset 1-7/7 rev 2 Krzysztof Błaszkowski
2016-05-30 11:19 ` Carlos Maiolino
2016-05-30 11:54 ` Krzysztof Błaszkowski
2016-05-31 12:25 ` Christoph Hellwig
2016-05-31 13:44 ` Krzysztof Błaszkowski
2016-06-01 7:33 ` Christoph Hellwig
2016-06-01 8:38 ` Krzysztof Błaszkowski
2016-06-01 8:41 ` freevxfs: hp-ux support. patchset r3, 2/4 Krzysztof Błaszkowski
2016-06-01 8:42 ` freevxfs: hp-ux support. patchset r3 3/4 Krzysztof Błaszkowski
2016-06-02 8:32 ` Christoph Hellwig
2016-06-02 9:18 ` Krzysztof Błaszkowski
2016-06-01 8:43 ` freevxfs: hp-ux support. patchset r3 4/4 Krzysztof Błaszkowski
2016-06-01 9:23 ` Krzysztof Błaszkowski [this message]
2016-06-02 8:25 ` freevxfs: hp-ux support. patchset 1-7/7 rev 2 Christoph Hellwig
2016-06-02 9:16 ` Krzysztof Błaszkowski
2016-06-10 14:46 ` freevxfs: hp-ux support. ( 1cce17017970c07) patchset 1/4 Krzysztof Błaszkowski
2016-06-01 9:27 ` freevxfs: hp-ux support. patchset 1-7/7 rev 2 Krzysztof Błaszkowski
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=1464773012.900.105.camel@linux-q3cb.site \
--to=kb@sysmikro.com.pl \
--cc=cmaiolino@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
/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.