All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Steve French <stfrench@microsoft.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [samba-ksmbd:for-next 16/16] fs/cifs/cifsfs.c:709:30: warning: implicit conversion from 'enum statusEnum' to 'enum tid_status_enum'
Date: Mon, 28 Mar 2022 09:33:13 +0800	[thread overview]
Message-ID: <202203280919.pdULZ8dR-lkp@intel.com> (raw)

tree:   git://git.samba.org/ksmbd.git for-next
head:   7e5c8c02911ba8d7e61d4fbd130215318343cf60
commit: 7e5c8c02911ba8d7e61d4fbd130215318343cf60 [16/16] smb3: cleanup and clarify status of tree connections
config: m68k-defconfig (https://download.01.org/0day-ci/archive/20220328/202203280919.pdULZ8dR-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.2.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
        git remote add samba-ksmbd git://git.samba.org/ksmbd.git
        git fetch --no-tags samba-ksmbd for-next
        git checkout 7e5c8c02911ba8d7e61d4fbd130215318343cf60
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=m68k SHELL=/bin/bash fs/cifs/

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

All warnings (new ones prefixed by >>):

   fs/cifs/cifsfs.c: In function 'cifs_umount_begin':
>> fs/cifs/cifsfs.c:709:30: warning: implicit conversion from 'enum statusEnum' to 'enum tid_status_enum' [-Wenum-conversion]
     709 |                 tcon->status = CifsExiting;
         |                              ^


vim +709 fs/cifs/cifsfs.c

   690	
   691	static void cifs_umount_begin(struct super_block *sb)
   692	{
   693		struct cifs_sb_info *cifs_sb = CIFS_SB(sb);
   694		struct cifs_tcon *tcon;
   695	
   696		if (cifs_sb == NULL)
   697			return;
   698	
   699		tcon = cifs_sb_master_tcon(cifs_sb);
   700	
   701		spin_lock(&cifs_tcp_ses_lock);
   702		if ((tcon->tc_count > 1) || (tcon->status == TID_EXITING)) {
   703			/* we have other mounts to same share or we have
   704			   already tried to force umount this and woken up
   705			   all waiting network requests, nothing to do */
   706			spin_unlock(&cifs_tcp_ses_lock);
   707			return;
   708		} else if (tcon->tc_count == 1)
 > 709			tcon->status = CifsExiting;
   710		spin_unlock(&cifs_tcp_ses_lock);
   711	
   712		/* cancel_brl_requests(tcon); */ /* BB mark all brl mids as exiting */
   713		/* cancel_notify_requests(tcon); */
   714		if (tcon->ses && tcon->ses->server) {
   715			cifs_dbg(FYI, "wake up tasks now - umount begin not complete\n");
   716			wake_up_all(&tcon->ses->server->request_q);
   717			wake_up_all(&tcon->ses->server->response_q);
   718			msleep(1); /* yield */
   719			/* we have to kick the requests once more */
   720			wake_up_all(&tcon->ses->server->response_q);
   721			msleep(1);
   722		}
   723	
   724		return;
   725	}
   726	

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

                 reply	other threads:[~2022-03-28  1:34 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 \
    --in-reply-to=202203280919.pdULZ8dR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stfrench@microsoft.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.