From: "David Härdeman" <david@hardeman.nu>
To: Timo Teras <timo.teras@iki.fi>
Cc: "Steve Dickson" <SteveD@redhat.com>,
linux-nfs@vger.kernel.org, "Timo Teräs" <timo.teras@gmail.com>
Subject: Re: [PATCH v2 0/5] rework access to /proc/net/rpc
Date: Wed, 10 Dec 2014 15:13:18 +0100 [thread overview]
Message-ID: <38d798fa4bd1434bbcc3c125509b2826@hardeman.nu> (raw)
In-Reply-To: <20141210080929.13c1fa30@vostro>
On 2014-12-10 07:09, Timo Teras wrote:
> On Tue, 09 Dec 2014 16:30:52 -0500
> Steve Dickson <SteveD@redhat.com> wrote:
>>>> My understanding these patches were needed to make nfs-utils
>>>> compatible with the musl c-library. That is the case, correct?
>
> Yes. It is because musl FILE implementation uses writev() and readv()
> with multiple buffers, and the kernel side does not handle that.
I should probably note in that case that my patches to gssd include a
call to fscanf, I'm guessing that'd be a problem for you?
> In my opinion the dynamic allocation is a step backward, rather then
> forwards. It adds potential failure (out of memory), is not required,
> and it does not add any features either.
>
> IMHO, "just because it used to be so" is a bad excuse. And it would
> just cause additional code making harder to debug and easier to fail.
> Why add complexity when it can be done simpler?
I think PATH_MAX is a good counter-example.
But I think we can at least agree that we're discussing coding style
now, which is a bit like discussing Emacs vs vi, and I doubt we'll ever
reach an agreement... :)
Regards,
David
next prev parent reply other threads:[~2014-12-10 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 8:16 [PATCH v2 0/5] rework access to /proc/net/rpc David Härdeman
2014-12-09 8:42 ` Timo Teras
2014-12-09 14:01 ` David Härdeman
2014-12-09 16:08 ` Steve Dickson
2014-12-09 20:26 ` David Härdeman
2014-12-09 21:30 ` Steve Dickson
2014-12-10 6:09 ` Timo Teras
2014-12-10 14:13 ` David Härdeman [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-02 13:41 Timo Teräs
2014-12-07 15:30 ` Steve Dickson
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=38d798fa4bd1434bbcc3c125509b2826@hardeman.nu \
--to=david@hardeman.nu \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=timo.teras@gmail.com \
--cc=timo.teras@iki.fi \
/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