public inbox for [email protected]
 help / color / mirror / Atom feed
From: kernel test robot <[email protected]>
To: "Jason A. Donenfeld" <[email protected]>
Cc: [email protected], Ammar Faizi <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	[email protected]
Subject: [ammarfaizi2-block:crng/random/jd/vdso 8/8] drivers/char/random.c:88:42: error: expected declaration specifiers or '...' before '_vdso_rng_data'
Date: Sat, 30 Jul 2022 11:44:25 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

tree:   https://github.com/ammarfaizi2/linux-block crng/random/jd/vdso
head:   65b88fc7d65669b6a7f4225aa00acf18b82a7682
commit: 65b88fc7d65669b6a7f4225aa00acf18b82a7682 [8/8] random: implement getrandom() in vDSO
config: csky-randconfig-r012-20220729 (https://download.01.org/0day-ci/archive/20220730/[email protected]/config)
compiler: csky-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/ammarfaizi2/linux-block/commit/65b88fc7d65669b6a7f4225aa00acf18b82a7682
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block crng/random/jd/vdso
        git checkout 65b88fc7d65669b6a7f4225aa00acf18b82a7682
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=csky SHELL=/bin/bash drivers/char/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>

All errors (new ones prefixed by >>):

>> drivers/char/random.c:88:42: error: expected declaration specifiers or '...' before '_vdso_rng_data'
      88 | DEFINE_VVAR_SINGLE(struct vdso_rng_data, _vdso_rng_data);
         |                                          ^~~~~~~~~~~~~~


vim +88 drivers/char/random.c

    63	
    64	/*********************************************************************
    65	 *
    66	 * Initialization and readiness waiting.
    67	 *
    68	 * Much of the RNG infrastructure is devoted to various dependencies
    69	 * being able to wait until the RNG has collected enough entropy and
    70	 * is ready for safe consumption.
    71	 *
    72	 *********************************************************************/
    73	
    74	/*
    75	 * crng_init is protected by base_crng->lock, and only increases
    76	 * its value (from empty->early->ready).
    77	 */
    78	static enum {
    79		CRNG_EMPTY = 0, /* Little to no entropy collected */
    80		CRNG_EARLY = 1, /* At least POOL_EARLY_BITS collected */
    81		CRNG_READY = 2  /* Fully initialized with POOL_READY_BITS collected */
    82	} crng_init __read_mostly = CRNG_EMPTY;
    83	static DEFINE_STATIC_KEY_FALSE(crng_is_ready);
    84	#define crng_ready() (static_branch_likely(&crng_is_ready) || crng_init >= CRNG_READY)
    85	/* Various types of waiters for crng_init->CRNG_READY transition. */
    86	static DECLARE_WAIT_QUEUE_HEAD(crng_init_wait);
    87	static struct fasync_struct *fasync;
  > 88	DEFINE_VVAR_SINGLE(struct vdso_rng_data, _vdso_rng_data);
    89	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-07-30  3:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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