diff options
author | John Kacur <jkacur@redhat.com> | 2009-10-11 22:24:25 +0200 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2009-10-14 17:36:54 +0200 |
commit | 55e858c8483af427144f33b42b818b30612b82b0 (patch) | |
tree | 300663182d53ca9ae77a54dce06066109e927a8f /drivers/parisc | |
parent | f96d3015e9f7f7fff4cab7ed1d467664cc980061 (diff) | |
download | kernel_samsung_smdk4412-55e858c8483af427144f33b42b818b30612b82b0.tar.gz kernel_samsung_smdk4412-55e858c8483af427144f33b42b818b30612b82b0.tar.bz2 kernel_samsung_smdk4412-55e858c8483af427144f33b42b818b30612b82b0.zip |
agp: Remove the BKL from agp_open
- Remove the BKL from agp_open
- Perform a few clean-ups.
Analysis:
---------
int minor is local to the function.
The following are protected by agp_fe.agp_mutex
struct agp_file_private *priv;
struct agp_client *client;
Call-outs:
kzalloc should be safe to call under the mutex_lock
agp_find_client_by_pid:
- agp_mmap calls that under agp_fe.agp_mutex which we hold in agp_open
- agpioc_reserve_wrap calls it without any locking what-so-ever.
- Is that an error? Or is that okay because it has pid that is
a unique handle?
agp_insert_file_private:
- This function only manipulates struct agp_file_private, once again
while agp_fe.agp_mutex is held
Signed-off-by: John Kacur <jkacur@redhat.com>
Acked-by: David Airlie <airlied@linux.ie>
LKML-Reference: <alpine.LFD.2.00.0910112216060.12574@localhost.localdomain>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'drivers/parisc')
0 files changed, 0 insertions, 0 deletions