mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Jiang Lu <lu.jiang@windriver.com>
Cc: kbuild-all@01.org, warrick.jiang@gmail.com,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: serial_core:recognize invalid pointer from userspace
Date: Wed, 9 Mar 2016 16:23:47 +0800	[thread overview]
Message-ID: <201603091629.akOMnD27%fengguang.wu@intel.com> (raw)
In-Reply-To: <1457510549-24801-2-git-send-email-lu.jiang@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]

Hi Jiang,

[auto build test WARNING on tty/tty-testing]
[also build test WARNING on v4.5-rc7 next-20160309]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]

url:    https://github.com/0day-ci/linux/commits/Jiang-Lu/serial_core-recognize-invalid-pointer-from-userspace/20160309-160641
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
config: i386-randconfig-x000-201610 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All warnings (new ones prefixed by >>):

   drivers/tty/serial/serial_core.c: In function 'uart_set_info':
>> drivers/tty/serial/serial_core.c:750:26: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
      new_info->iomem_base = (unsigned char *)uport->mapbase;
                             ^

vim +750 drivers/tty/serial/serial_core.c

   734		new_info->irq = irq_canonicalize(new_info->irq);
   735		close_delay = msecs_to_jiffies(new_info->close_delay * 10);
   736		closing_wait = new_info->closing_wait == ASYNC_CLOSING_WAIT_NONE ?
   737				ASYNC_CLOSING_WAIT_NONE :
   738				msecs_to_jiffies(new_info->closing_wait * 10);
   739	
   740	
   741		change_irq  = !(uport->flags & UPF_FIXED_PORT)
   742			&& new_info->irq != uport->irq;
   743	
   744		/*
   745		 * Since changing the 'type' of the port changes its resource
   746		 * allocations, we should treat type changes the same as
   747		 * IO port changes.
   748		 */
   749		if ((unsigned long)new_info->iomem_base == 0xffffffff)
 > 750			new_info->iomem_base = (unsigned char *)uport->mapbase;
   751	
   752		change_port = !(uport->flags & UPF_FIXED_PORT)
   753			&& (new_port != uport->iobase ||
   754			    (unsigned long)new_info->iomem_base != uport->mapbase ||
   755			    new_info->hub6 != uport->hub6 ||
   756			    new_info->io_type != uport->iotype ||
   757			    new_info->iomem_reg_shift != uport->regshift ||
   758			    new_info->type != uport->type);

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 23395 bytes --]

      reply	other threads:[~2016-03-09  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  8:02 Jiang Lu
2016-03-09  8:02 ` Jiang Lu
2016-03-09  8:23   ` kbuild test robot [this message]

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=201603091629.akOMnD27%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lu.jiang@windriver.com \
    --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

all inboxes | Powered by JetHome®