From: Jim Nelson <james4765@verizon.net>
To: Domen Puncer <domen@coderock.org>
Cc: kernel-janitors@lists.osdl.org, linux-kernel@vger.kernel.org,
akpm@osdl.org
Subject: [KJ] Re: lcd: fix memory leak, code cleanup
Date: Wed, 22 Dec 2004 03:45:29 +0000 [thread overview]
Message-ID: <41C8EDD9.7070007@verizon.net> (raw)
In-Reply-To: <20041221120607.GA30293@nd47.coderock.org>
[-- Attachment #1: Type: text/plain, Size: 2828 bytes --]
Domen Puncer wrote:
> On 20/12/04 19:50 -0600, James Nelson wrote:
>
>>This patch addresses the following issues:
>>
>>Fix log-spamming and cryptic error messages, and add KERN_ constants.
>>Convert some ints to unsigned ints.
>>Add checks for CAP_SYS_ADMIN for FLASH_Burn and FLASH_Erase ioctls.
>>Identify use of global variable.
>>Fix memory leak in FLASH_Burn ioctl.
>>Fix error return codes in lcd_ioctl().
>>Move variable "index" in lcd_ioctl() to smaller scope to reduce memory usage.
>>Convert cli()/sti() to spin_lock_irqsave()/spin_unlock_irqrestore().
>>Fix legibility issues in FLASH_Burn ioctl.
>>
>
>
>
>>- cli();
>>+ spin_lock_irqsave(&lcd_lock, flags);
>> for (index = 0; index < (128); index++) {
>>
>> WRITE_FLASH(kFlash_Addr1,
>>@@ -480,32 +485,30 @@
>> kFlash_Data2);
>> WRITE_FLASH(kFlash_Addr1,
>> kFlash_Prog);
>>- *((volatile unsigned char *)
>>- burn_addr) =
>>- (volatile unsigned char) rom[index];
>>-
>>- while ((!dqpoll
>>- (burn_addr,
>>- (volatile unsigned char)
>>- rom[index]))
>>- && (!timeout(burn_addr))) {
>>- }
>>+ *((volatile unsigned char *)burn_addr) =
>>+ (volatile unsigned char) rom[index];
>>+
>>+ while ((!dqpoll (burn_addr,
>>+ (volatile unsigned char)
>>+ rom[index])) &&
>>+ (!timeout(burn_addr))) { }
>> burn_addr++;
>> }
>>- restore_flags(flags);
>>- if (*
>>- ((volatile unsigned char *) (burn_addr
>>- - 1)) ==
>>- (volatile unsigned char) rom[index -
>>- 1]) {
>>+ spin_unlock_irqrestore(&lcd_lock, flags);
>
>
>
> Although this will work, i think local_irq_{disable,enable} is the right
> solution (we don't protect any data, just make sure timings are right).
>
Since the Cobalt systems are single-processor, there's no functional difference
between disabling global and local interrupts.
> For making it SMP safe, easiest/sane solution seems semaphore in
> lcd_dev, which is down_interruptible(), at beginning of read, write
> and ioctl.
>
> Comments?
>
>
> Domen
>
True, but it would requre making struct lcd_display a global variable, and involve
reworking just about the whole driver, since it is declared as a local variable in
individual ioctl case statements, and others use the variable defined at the top
of the ioctl function. OTOH, it would reduce stack usage...
I was trying to minimize any mucking about with the functional parts of the
driver, since I don't have the hardware to test it.
Since ioctls are still protected by the BKL right now (and this thing is pretty
much nothing but an ioctl interface), I don't see too much of a problem with this
driver. More complete drivers, however, would definitely benefit from it, and is
something I'll keep in mind.
Jim
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
WARNING: multiple messages have this Message-ID (diff)
From: Jim Nelson <james4765@verizon.net>
To: Domen Puncer <domen@coderock.org>
Cc: kernel-janitors@lists.osdl.org, linux-kernel@vger.kernel.org,
akpm@osdl.org
Subject: Re: lcd: fix memory leak, code cleanup
Date: Tue, 21 Dec 2004 22:45:29 -0500 [thread overview]
Message-ID: <41C8EDD9.7070007@verizon.net> (raw)
In-Reply-To: <20041221120607.GA30293@nd47.coderock.org>
Domen Puncer wrote:
> On 20/12/04 19:50 -0600, James Nelson wrote:
>
>>This patch addresses the following issues:
>>
>>Fix log-spamming and cryptic error messages, and add KERN_ constants.
>>Convert some ints to unsigned ints.
>>Add checks for CAP_SYS_ADMIN for FLASH_Burn and FLASH_Erase ioctls.
>>Identify use of global variable.
>>Fix memory leak in FLASH_Burn ioctl.
>>Fix error return codes in lcd_ioctl().
>>Move variable "index" in lcd_ioctl() to smaller scope to reduce memory usage.
>>Convert cli()/sti() to spin_lock_irqsave()/spin_unlock_irqrestore().
>>Fix legibility issues in FLASH_Burn ioctl.
>>
>
>
>
>>- cli();
>>+ spin_lock_irqsave(&lcd_lock, flags);
>> for (index = 0; index < (128); index++) {
>>
>> WRITE_FLASH(kFlash_Addr1,
>>@@ -480,32 +485,30 @@
>> kFlash_Data2);
>> WRITE_FLASH(kFlash_Addr1,
>> kFlash_Prog);
>>- *((volatile unsigned char *)
>>- burn_addr) =
>>- (volatile unsigned char) rom[index];
>>-
>>- while ((!dqpoll
>>- (burn_addr,
>>- (volatile unsigned char)
>>- rom[index]))
>>- && (!timeout(burn_addr))) {
>>- }
>>+ *((volatile unsigned char *)burn_addr) =
>>+ (volatile unsigned char) rom[index];
>>+
>>+ while ((!dqpoll (burn_addr,
>>+ (volatile unsigned char)
>>+ rom[index])) &&
>>+ (!timeout(burn_addr))) { }
>> burn_addr++;
>> }
>>- restore_flags(flags);
>>- if (*
>>- ((volatile unsigned char *) (burn_addr
>>- - 1)) ==
>>- (volatile unsigned char) rom[index -
>>- 1]) {
>>+ spin_unlock_irqrestore(&lcd_lock, flags);
>
>
>
> Although this will work, i think local_irq_{disable,enable} is the right
> solution (we don't protect any data, just make sure timings are right).
>
Since the Cobalt systems are single-processor, there's no functional difference
between disabling global and local interrupts.
> For making it SMP safe, easiest/sane solution seems semaphore in
> lcd_dev, which is down_interruptible(), at beginning of read, write
> and ioctl.
>
> Comments?
>
>
> Domen
>
True, but it would requre making struct lcd_display a global variable, and involve
reworking just about the whole driver, since it is declared as a local variable in
individual ioctl case statements, and others use the variable defined at the top
of the ioctl function. OTOH, it would reduce stack usage...
I was trying to minimize any mucking about with the functional parts of the
driver, since I don't have the hardware to test it.
Since ioctls are still protected by the BKL right now (and this thing is pretty
much nothing but an ioctl interface), I don't see too much of a problem with this
driver. More complete drivers, however, would definitely benefit from it, and is
something I'll keep in mind.
Jim
next prev parent reply other threads:[~2004-12-22 3:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 1:50 [KJ] [PATCH] lcd: fix memory leak, code cleanup James Nelson
2004-12-21 1:50 ` James Nelson
2004-12-21 8:15 ` [KJ] " walter harms
2004-12-21 12:06 ` [KJ] " Domen Puncer
2004-12-21 12:06 ` Domen Puncer
2004-12-22 3:45 ` Jim Nelson [this message]
2004-12-22 3:45 ` Jim Nelson
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=41C8EDD9.7070007@verizon.net \
--to=james4765@verizon.net \
--cc=akpm@osdl.org \
--cc=domen@coderock.org \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-kernel@vger.kernel.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.