All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] vt: don't use kmalloc() for the unicode screen buffer
Date: Sun, 29 Mar 2020 08:13:05 +0800	[thread overview]
Message-ID: <202003290801.rHW7R4P9%lkp@intel.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.2003281745280.2671@knanqh.ubzr>

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

Hi Nicolas,

I love your patch! Yet something to improve:

[auto build test ERROR on tty/tty-testing]
[also build test ERROR on v5.6-rc7 next-20200327]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Nicolas-Pitre/vt-don-t-use-kmalloc-for-the-unicode-screen-buffer/20200329-060123
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
config: mips-nlm_xlp_defconfig (attached as .config)
compiler: mips64-linux-gcc (GCC) 9.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=9.2.0 make.cross ARCH=mips 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All error/warnings (new ones prefixed by >>):

   drivers/tty/vt/vt.c: In function 'vc_uniscr_alloc':
>> drivers/tty/vt/vt.c:353:6: error: implicit declaration of function 'vmalloc'; did you mean 'kvmalloc'? [-Werror=implicit-function-declaration]
     353 |  p = vmalloc(memsize);
         |      ^~~~~~~
         |      kvmalloc
>> drivers/tty/vt/vt.c:353:4: warning: assignment to 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
     353 |  p = vmalloc(memsize);
         |    ^
   drivers/tty/vt/vt.c: In function 'vc_uniscr_set':
>> drivers/tty/vt/vt.c:369:2: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
     369 |  vfree(vc->vc_uni_screen);
         |  ^~~~~
         |  kvfree
   cc1: some warnings being treated as errors

vim +353 drivers/tty/vt/vt.c

   343	
   344	static struct uni_screen *vc_uniscr_alloc(unsigned int cols, unsigned int rows)
   345	{
   346		struct uni_screen *uniscr;
   347		void *p;
   348		unsigned int memsize, i;
   349	
   350		/* allocate everything in one go */
   351		memsize = cols * rows * sizeof(char32_t);
   352		memsize += rows * sizeof(char32_t *);
 > 353		p = vmalloc(memsize);
   354		if (!p)
   355			return NULL;
   356	
   357		/* initial line pointers */
   358		uniscr = p;
   359		p = uniscr->lines + rows;
   360		for (i = 0; i < rows; i++) {
   361			uniscr->lines[i] = p;
   362			p += cols * sizeof(char32_t);
   363		}
   364		return uniscr;
   365	}
   366	
   367	static void vc_uniscr_set(struct vc_data *vc, struct uni_screen *new_uniscr)
   368	{
 > 369		vfree(vc->vc_uni_screen);
   370		vc->vc_uni_screen = new_uniscr;
   371	}
   372	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 21499 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: kbuild-all@lists.01.org, "gregkh@linuxfoundation.org,
	Chen Wandun" <chenwandun@huawei.com>,
	Adam Borowski <kilobyte@angband.pl>,
	jslaby@suse.com, daniel.vetter@ffwll.ch, sam@ravnborg.org,
	b.zolnierkie@samsung.com, lukas@wunner.de, ghalat@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vt: don't use kmalloc() for the unicode screen buffer
Date: Sun, 29 Mar 2020 08:13:05 +0800	[thread overview]
Message-ID: <202003290801.rHW7R4P9%lkp@intel.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.2003281745280.2671@knanqh.ubzr>

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

Hi Nicolas,

I love your patch! Yet something to improve:

[auto build test ERROR on tty/tty-testing]
[also build test ERROR on v5.6-rc7 next-20200327]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Nicolas-Pitre/vt-don-t-use-kmalloc-for-the-unicode-screen-buffer/20200329-060123
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
config: mips-nlm_xlp_defconfig (attached as .config)
compiler: mips64-linux-gcc (GCC) 9.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=9.2.0 make.cross ARCH=mips 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All error/warnings (new ones prefixed by >>):

   drivers/tty/vt/vt.c: In function 'vc_uniscr_alloc':
>> drivers/tty/vt/vt.c:353:6: error: implicit declaration of function 'vmalloc'; did you mean 'kvmalloc'? [-Werror=implicit-function-declaration]
     353 |  p = vmalloc(memsize);
         |      ^~~~~~~
         |      kvmalloc
>> drivers/tty/vt/vt.c:353:4: warning: assignment to 'void *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
     353 |  p = vmalloc(memsize);
         |    ^
   drivers/tty/vt/vt.c: In function 'vc_uniscr_set':
>> drivers/tty/vt/vt.c:369:2: error: implicit declaration of function 'vfree'; did you mean 'kvfree'? [-Werror=implicit-function-declaration]
     369 |  vfree(vc->vc_uni_screen);
         |  ^~~~~
         |  kvfree
   cc1: some warnings being treated as errors

vim +353 drivers/tty/vt/vt.c

   343	
   344	static struct uni_screen *vc_uniscr_alloc(unsigned int cols, unsigned int rows)
   345	{
   346		struct uni_screen *uniscr;
   347		void *p;
   348		unsigned int memsize, i;
   349	
   350		/* allocate everything in one go */
   351		memsize = cols * rows * sizeof(char32_t);
   352		memsize += rows * sizeof(char32_t *);
 > 353		p = vmalloc(memsize);
   354		if (!p)
   355			return NULL;
   356	
   357		/* initial line pointers */
   358		uniscr = p;
   359		p = uniscr->lines + rows;
   360		for (i = 0; i < rows; i++) {
   361			uniscr->lines[i] = p;
   362			p += cols * sizeof(char32_t);
   363		}
   364		return uniscr;
   365	}
   366	
   367	static void vc_uniscr_set(struct vc_data *vc, struct uni_screen *new_uniscr)
   368	{
 > 369		vfree(vc->vc_uni_screen);
   370		vc->vc_uni_screen = new_uniscr;
   371	}
   372	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 21499 bytes --]

  parent reply	other threads:[~2020-03-29  0:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 21:59 [PATCH] vt: don't use kmalloc() for the unicode screen buffer Nicolas Pitre
2020-03-28 23:35 ` kbuild test robot
2020-03-28 23:35   ` kbuild test robot
2020-03-29  0:13 ` kbuild test robot [this message]
2020-03-29  0:13   ` kbuild test robot
2020-03-29  2:25 ` [PATCH v2] " Nicolas Pitre
2020-03-30 19:07   ` Sam Ravnborg
2020-03-31  8:43     ` Daniel Vetter
2020-03-31  9:30       ` Greg KH

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=202003290801.rHW7R4P9%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.