From: Domen Puncer <domen@coderock.org>
To: James Nelson <james4765@verizon.net>
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 13:06:07 +0100 [thread overview]
Message-ID: <20041221120607.GA30293@nd47.coderock.org> (raw)
In-Reply-To: <20041221015120.29110.98832.48706@localhost.localdomain>
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).
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
next prev parent reply other threads:[~2004-12-21 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 1:50 [PATCH] lcd: fix memory leak, code cleanup James Nelson
2004-12-21 12:06 ` Domen Puncer [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=20041221120607.GA30293@nd47.coderock.org \
--to=domen@coderock.org \
--cc=akpm@osdl.org \
--cc=james4765@verizon.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox