From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nitin Gupta <ngupta@vflare.org>
Cc: Minchan Kim <minchan@kernel.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 5/6] zsmalloc: remove unnecessary type casting
Date: Wed, 25 Apr 2012 10:56:39 -0700 [thread overview]
Message-ID: <20120425175639.GA14974@kroah.com> (raw)
In-Reply-To: <4F97FD9D.9090105@vflare.org>
On Wed, Apr 25, 2012 at 09:35:25AM -0400, Nitin Gupta wrote:
> On 04/25/2012 02:23 AM, Minchan Kim wrote:
>
> > Let's remove unnecessary type casting of (void *).
> >
> > Signed-off-by: Minchan Kim <minchan@kernel.org>
> > ---
> > drivers/staging/zsmalloc/zsmalloc-main.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc-main.c
> > index b7d31cc..ff089f8 100644
> > --- a/drivers/staging/zsmalloc/zsmalloc-main.c
> > +++ b/drivers/staging/zsmalloc/zsmalloc-main.c
> > @@ -644,8 +644,7 @@ void zs_free(struct zs_pool *pool, void *obj)
> > spin_lock(&class->lock);
> >
> > /* Insert this object in containing zspage's freelist */
> > - link = (struct link_free *)((unsigned char *)kmap_atomic(f_page)
> > - + f_offset);
> > + link = (struct link_free *)(kmap_atomic(f_page) + f_offset);
> > link->next = first_page->freelist;
> > kunmap_atomic(link);
> > first_page->freelist = obj;
>
>
>
> Incrementing a void pointer looks weired and should not be allowed by C
> compilers though gcc and clang seem to allow this without any warnings.
> (fortunately C++ forbids incrementing void pointers)
Huh? A void pointer can safely be incremented by C I thought, do you
have a pointer to where in the reference it says it is "unspecified"?
> So, we should keep this cast to unsigned char pointer to avoid relying
> on a non-standard, compiler specific behavior.
I do agree about this, more people are starting to build the kernel with
other compilers than gcc, so it would be nice to ensure that we get
stuff like this right.
thanks,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-25 17:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 6:23 [PATCH 0/6] zsmalloc: clean up and fix arch dependency Minchan Kim
2012-04-25 6:23 ` [PATCH 1/6] zsmalloc: use PageFlag macro instead of [set|test]_bit Minchan Kim
2012-04-25 12:43 ` Nitin Gupta
2012-04-25 6:23 ` [PATCH 2/6] zsmalloc: remove unnecessary alignment Minchan Kim
2012-04-25 12:53 ` Nitin Gupta
2012-04-26 1:42 ` Minchan Kim
2012-05-03 5:16 ` Nitin Gupta
2012-04-25 6:23 ` [PATCH 3/6] zsmalloc: rename zspage_order with zspage_pages Minchan Kim
2012-04-25 13:03 ` Nitin Gupta
2012-04-26 1:46 ` Minchan Kim
2012-04-25 6:23 ` [PATCH 4/6] zsmalloc: add/fix function comment Minchan Kim
2012-04-25 13:27 ` Nitin Gupta
2012-04-26 1:51 ` Minchan Kim
2012-04-25 6:23 ` [PATCH 5/6] zsmalloc: remove unnecessary type casting Minchan Kim
2012-04-25 13:35 ` Nitin Gupta
2012-04-25 17:56 ` Greg Kroah-Hartman [this message]
2012-04-25 18:13 ` Nitin Gupta
2012-04-26 1:58 ` Minchan Kim
2012-04-25 6:23 ` [PATCH 6/6] zsmalloc: make zsmalloc portable Minchan Kim
2012-04-25 14:32 ` Nitin Gupta
2012-04-25 15:40 ` Dan Magenheimer
2012-04-26 2:03 ` Minchan Kim
2012-04-26 5:07 ` Minchan Kim
2012-04-30 16:24 ` Seth Jennings
2012-04-25 16:37 ` Seth Jennings
2012-04-26 2:04 ` Minchan Kim
2012-05-07 15:14 ` Seth Jennings
2012-05-08 0:46 ` Minchan Kim
2012-04-26 2:11 ` Minchan Kim
2012-04-25 12:41 ` [PATCH 0/6] zsmalloc: clean up and fix arch dependency Nitin Gupta
2012-04-26 1:20 ` Minchan Kim
2012-04-25 18:14 ` Greg Kroah-Hartman
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=20120425175639.GA14974@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.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