From: Rob Jones <rob.jones@codethink.co.uk>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] fs: replace int param with size_t for seq_open_private()
Date: Tue, 02 Sep 2014 09:29:37 +0100 [thread overview]
Message-ID: <54057FF1.2010805@codethink.co.uk> (raw)
In-Reply-To: <20140901212250.GJ7996@ZenIV.linux.org.uk>
On 01/09/14 22:22, Al Viro wrote:
> On Mon, Sep 01, 2014 at 03:38:51PM +0100, Rob Jones wrote:
>>>> kmalloc where it is expected to be a size_t.
>>>
>>> Which is a mistake too because allocations are never that large.
>>
>> Yet.
>
> *raised eyebrow*
>
> You do realize that kmalloc() gives physically contiguous allocation, right?
Do please try to not be quite so patronizing. It's very counter-
productive.
> And refuses to allocate more than KMALLOC_MAX_SIZE, while we are at it.
> With allocations anywhere near such range being very heavily discouraged.
>
> There might or might not be point in using size_t for kmalloc() argument,
> but "future-proofing" isn't it.
Indeed, and I am following up those arguments with people that may want
to be constructive.
>
>
--
Rob Jones
Codethink Ltd
mailto:rob.jones@codethink.co.uk
tel:+44 161 236 5575
next prev parent reply other threads:[~2014-09-02 8:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 13:43 [PATCH] fs: replace int param with size_t for seq_open_private() Alexey Dobriyan
2014-09-01 13:54 ` Rob Jones
2014-09-01 14:13 ` Alexey Dobriyan
2014-09-01 14:38 ` Rob Jones
2014-09-01 21:22 ` Al Viro
2014-09-02 8:29 ` Rob Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-01 13:17 Rob Jones
2014-09-01 15:36 ` Al Viro
2014-09-01 15:53 ` Rob Jones
2014-09-11 16:25 ` Rob Jones
2014-09-12 14:16 ` Richard Weinberger
2014-09-12 14:43 ` Rob Jones
2014-09-01 13:13 Rob Jones
2014-09-01 13:15 ` Rob Jones
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=54057FF1.2010805@codethink.co.uk \
--to=rob.jones@codethink.co.uk \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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.