All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Xin Chen <xin.chen2@oss.qualcomm.com>,
	gregkh@linuxfoundation.org, jirislaby@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, stable@vger.kernel.org,
	liulzhao@qti.qualcomm.com, cheng.jiang@oss.qualcomm.com,
	cxin@qti.qualcomm.com, Xin Chen <xin.chen2@oss.qualcomm.com>
Subject: Re: [PATCH v2] tty: n_tty: use kvzalloc/kvfree for line discipline data
Date: Fri, 21 Aug 2026 14:48:32 +0800	[thread overview]
Message-ID: <202608211421.J0U0ljJ6-lkp@intel.com> (raw)
In-Reply-To: <20260818070324.136726-1-xin.chen2@oss.qualcomm.com>

Hi Xin,

kernel test robot noticed the following build errors:

[auto build test ERROR on tty/tty-testing]
[also build test ERROR on tty/tty-next tty/tty-linus linus/master v7.2 next-20260819]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Xin-Chen/tty-n_tty-use-kvzalloc-kvfree-for-line-discipline-data/20260818-150324
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
patch link:    https://lore.kernel.org/r/20260818070324.136726-1-xin.chen2%40oss.qualcomm.com
patch subject: [PATCH v2] tty: n_tty: use kvzalloc/kvfree for line discipline data
config: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20260821/202608211421.J0U0ljJ6-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260821/202608211421.J0U0ljJ6-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608211421.J0U0ljJ6-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/tty/n_tty.c: In function 'n_tty_open':
>> drivers/tty/n_tty.c:1890:15: error: assignment to 'struct n_tty_data *' from incompatible pointer type 'struct n_tty_data **' [-Wincompatible-pointer-types]
    1890 |         ldata = kvzalloc_obj(ldata);
         |               ^


vim +1890 drivers/tty/n_tty.c

  1876	
  1877	/**
  1878	 * n_tty_open		-	open an ldisc
  1879	 * @tty: terminal to open
  1880	 *
  1881	 * Called when this line discipline is being attached to the terminal device.
  1882	 * Can sleep. Called serialized so that no other events will occur in parallel.
  1883	 * No further open will occur until a close.
  1884	 */
  1885	static int n_tty_open(struct tty_struct *tty)
  1886	{
  1887		struct n_tty_data *ldata;
  1888	
  1889		/* Currently a malloc failure here can panic */
> 1890		ldata = kvzalloc_obj(ldata);
  1891		if (!ldata)
  1892			return -ENOMEM;
  1893	
  1894		ldata->overrun_time = jiffies;
  1895		mutex_init(&ldata->atomic_read_lock);
  1896		mutex_init(&ldata->output_lock);
  1897	
  1898		tty->disc_data = ldata;
  1899		tty->closing = 0;
  1900		/* indicate buffer work may resume */
  1901		clear_bit(TTY_LDISC_HALTED, &tty->flags);
  1902		n_tty_set_termios(tty, NULL);
  1903		tty_unthrottle(tty);
  1904		return 0;
  1905	}
  1906	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2026-08-21  6:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 13:55 [PATCH v1] tty: n_tty: use kvzalloc/kvfree for line discipline data Xin Chen
2026-08-17 14:14 ` Greg KH
2026-08-18  3:09   ` Xin Chen
2026-08-18  6:05     ` Greg KH
2026-08-18  6:22       ` Xin Chen
2026-08-17 14:16 ` Greg KH
2026-08-17 14:49   ` Greg KH
2026-08-18  6:02     ` Xin Chen
2026-08-18  6:34       ` Greg KH
2026-08-18  6:58         ` Xin Chen
2026-08-18  7:34           ` Greg KH
2026-08-21  8:06             ` Xin Chen
2026-08-18  3:31   ` Xin Chen
2026-08-18  6:07     ` Greg KH
2026-08-18  6:39       ` Xin Chen
2026-08-18  7:03 ` [PATCH v2] " Xin Chen
2026-08-18  7:15   ` Jiri Slaby
2026-08-18  7:23     ` Xin Chen
2026-08-21  6:48   ` kernel test robot [this message]
2026-08-21  8:35   ` kernel 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=202608211421.J0U0ljJ6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cheng.jiang@oss.qualcomm.com \
    --cc=cxin@qti.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=liulzhao@qti.qualcomm.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=xin.chen2@oss.qualcomm.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 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.