From: Jiang Lu <lu.jiang@windriver.com>
To: warrick.jiang@gmail.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: serial_core:recognize invalid pointer from userspace
Date: Wed, 9 Mar 2016 16:02:28 +0800 [thread overview]
Message-ID: <1457510549-24801-1-git-send-email-lu.jiang@windriver.com> (raw)
Hi,
When running setserial, application issue a TIOCGSERIAL iotcl to get serial setting, then update
serial setting with TIOCSSERIAL ioctl. It always failed with TIOCSSERIAL ioctl, for application
pass 0xffffffff for iomem_base in serial_struct to kernel.
On 32bit rootfs & 64bit kernel, compat_ioctl use 0xffffffff as a magic number to mark invalid pointer
for iomem_base in serial_struct when truncating a 64bit pointer into 32bit.
Serial driver need recognize this invalid pointer when parsing serial_struct from userspace.
Thanks
Jiang Lu
next reply other threads:[~2016-03-09 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 8:02 Jiang Lu [this message]
2016-03-09 8:02 ` serial_core:recognize invalid pointer from userspace Jiang Lu
2016-03-09 8:23 ` kbuild test robot
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=1457510549-24801-1-git-send-email-lu.jiang@windriver.com \
--to=lu.jiang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=warrick.jiang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox