From: Alexey Dobriyan <adobriyan@gmail.com>
To: akpm@osdl.org
Cc: julien.tinnes@francetelecom.com, linux-kernel@vger.kernel.org
Subject: Re: potential-null-pointer-dereference-in-amiga-serial-driver.patch added to -mm tree
Date: Tue, 31 May 2005 19:49:15 +0400 [thread overview]
Message-ID: <200505311949.15449.adobriyan@gmail.com> (raw)
In-Reply-To: <200505310909.j4V98xBR008727@shell0.pdx.osdl.net>
On Tuesday 31 May 2005 13:08, akpm@osdl.org wrote:
> A pointer is dereferenced before it is null-checked.
> --- 25/drivers/char/amiserial.c~potential-null-pointer-dereference-in-amiga-serial-driver
> +++ 25-akpm/drivers/char/amiserial.c
> static void rs_put_char(struct tty_struct *tty, unsigned char ch)
> {
> - struct async_struct *info = (struct async_struct *)tty->driver_data;
> + struct async_struct *info;
> unsigned long flags;
>
> + if (!tty)
> + return;
Can ->put_char be ever called with tty being NULL? From my reading of
drivers/char/n_tty.c it can't.
Every single time ->put_char is used a-la
tty->driver->put_char(tty, '\r');
So, tty will be dereferenced before function call. Same for static inline
put_char() there.
> +
> + info = tty->driver_data;
> static int rs_write(struct tty_struct * tty, const unsigned char *buf, int count)
> {
> - struct async_struct *info = (struct async_struct *)tty->driver_data;
> + struct async_struct *info;
> unsigned long flags;
>
> + if (!tty)
> + return 0;
Same question.
> +
> + info = tty->driver_data;
next parent reply other threads:[~2005-05-31 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505310909.j4V98xBR008727@shell0.pdx.osdl.net>
2005-05-31 15:49 ` Alexey Dobriyan [this message]
2005-05-31 12:22 ` potential-null-pointer-dereference-in-amiga-serial-driver.patch added to -mm tree Marcelo Tosatti
2005-06-02 5:21 ` Greg KH
2005-06-03 7:58 ` Marcelo Tosatti
2005-06-09 9:31 ` Julien TINNES
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=200505311949.15449.adobriyan@gmail.com \
--to=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=julien.tinnes@francetelecom.com \
--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