From: Andres Salomon <dilinger@queued.net>
To: Thiago Galesi <thiagogalesi@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fb: Remove use of lock_kernel / unlock_kernel in fbmem
Date: Fri, 18 Apr 2008 13:41:12 -0400 [thread overview]
Message-ID: <20080418134112.2a9c5929@ephemeral> (raw)
In-Reply-To: <200804162000.59587.thiagogalesi@gmail.com>
On Wed, 16 Apr 2008 20:00:59 -0300
Thiago Galesi <thiagogalesi@gmail.com> wrote:
>
> This patch removes lock_kernel(), unlock_kernel() usage in fbmem.c and replaces it with a mutex
>
> Signed-off-by: Thiago Galesi <thiagogalesi@gmail.com>
>
[...]
> @@ -1413,6 +1435,8 @@ register_framebuffer(struct fb_info *fb_
>
> event.info = fb_info;
> fb_notifier_call_chain(FB_EVENT_FB_REGISTERED, &event);
> +
> + mutex_init(&fb_info->hwlock);
> return 0;
> }
>
Just a minor nit; in general, I'd think you would want to completely
initialize the structure (including calling mutex_init) before
registering the structure with the rest of the system (in this case,
with registered_fb and *_call_notifier_chain). Initializing after
registration is just asking for a race conditions.
--
Need a kernel or Debian developer? Contact me, I'm looking for contracts.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
WARNING: multiple messages have this Message-ID (diff)
From: Andres Salomon <dilinger@queued.net>
To: Thiago Galesi <thiagogalesi@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] fb: Remove use of lock_kernel / unlock_kernel in fbmem
Date: Fri, 18 Apr 2008 13:41:12 -0400 [thread overview]
Message-ID: <20080418134112.2a9c5929@ephemeral> (raw)
In-Reply-To: <200804162000.59587.thiagogalesi@gmail.com>
On Wed, 16 Apr 2008 20:00:59 -0300
Thiago Galesi <thiagogalesi@gmail.com> wrote:
>
> This patch removes lock_kernel(), unlock_kernel() usage in fbmem.c and replaces it with a mutex
>
> Signed-off-by: Thiago Galesi <thiagogalesi@gmail.com>
>
[...]
> @@ -1413,6 +1435,8 @@ register_framebuffer(struct fb_info *fb_
>
> event.info = fb_info;
> fb_notifier_call_chain(FB_EVENT_FB_REGISTERED, &event);
> +
> + mutex_init(&fb_info->hwlock);
> return 0;
> }
>
Just a minor nit; in general, I'd think you would want to completely
initialize the structure (including calling mutex_init) before
registering the structure with the rest of the system (in this case,
with registered_fb and *_call_notifier_chain). Initializing after
registration is just asking for a race conditions.
--
Need a kernel or Debian developer? Contact me, I'm looking for contracts.
next prev parent reply other threads:[~2008-04-18 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 14:50 [PATCH] fb: Remove use of lock_kernel / unlock_kernel in fbmem Thiago Galesi
2008-04-16 5:17 ` Andrew Morton
2008-04-16 5:17 ` [Linux-fbdev-devel] " Andrew Morton
2008-04-16 23:00 ` Thiago Galesi
2008-04-16 23:00 ` [Linux-fbdev-devel] " Thiago Galesi
2008-04-18 17:41 ` Andres Salomon [this message]
2008-04-18 17:41 ` Andres Salomon
2008-04-19 0:54 ` Thiago Galesi
2008-04-19 0:54 ` [Linux-fbdev-devel] " Thiago Galesi
2008-04-19 1:45 ` Andres Salomon
2008-04-19 1:45 ` [Linux-fbdev-devel] " Andres Salomon
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=20080418134112.2a9c5929@ephemeral \
--to=dilinger@queued.net \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thiagogalesi@gmail.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 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.