All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-media@vger.kernel.org
Cc: Andreas Oberritter <obi@linuxtv.org>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Steven Toth <stoth@linuxtv.org>
Subject: Re: [PATCH] Use kzalloc for frontend states to have struct dvb_frontend properly initialized
Date: Fri, 19 Jun 2009 14:41:12 +0200	[thread overview]
Message-ID: <200906191441.13521.zzam@gentoo.org> (raw)
In-Reply-To: <4A3B809D.7050709@linuxtv.org>

On Freitag, 19. Juni 2009, Andreas Oberritter wrote:
> Hello Matthias,
>
> Matthias Schwarzott wrote:
> > This patch changes most frontend drivers to allocate their state
> > structure via kzalloc and not kmalloc. This is done to properly
> > initialize the embedded "struct dvb_frontend frontend" field, that they
> > all have.
> >
> > The visible effect of this struct being uninitalized is, that the member
> > "id" that is used to set the name of kernel thread is totally random.
> >
> > [...]
> >
> > Signed-off-by: Matthias Schwarzott <zzam@gentoo.org>
>
> I still think that this id doesn't belong into struct dvb_frontend and
> should be private to the drivers, but using kzalloc is a good idea in
> every case. Did you verify that none of the drivers does an additional
> memset?
Yes, I did verify that. There are no memset calls for that memory.

> If so, you can add my "Acked-by: Andreas Oberritter 
> <obi@linuxtv.org>".
>
Regards
Matthias

  reply	other threads:[~2009-06-19 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 11:21 [PATCH] Use kzalloc for frontend states to have struct dvb_frontend properly initialized Matthias Schwarzott
2009-06-19 12:12 ` Andreas Oberritter
2009-06-19 12:41   ` Matthias Schwarzott [this message]
2009-06-19 13:15     ` Devin Heitmueller

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=200906191441.13521.zzam@gentoo.org \
    --to=zzam@gentoo.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=obi@linuxtv.org \
    --cc=stoth@linuxtv.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.