From: kernel test robot <lkp@intel.com>
To: Henry Martin <bsdhenrymartin@gmail.com>,
Paulo Alcantara <pc@manguebit.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Tom Talpey <tom@talpey.com>, Bharath SM <bharathsm@microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org, linux-kernel@vger.kernel.org,
Henry Martin <bsdhenrymartin@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] cifs: fix UAF read of server->hostname in cifs_get_spnego_key()
Date: Thu, 29 Oct 2026 02:58:42 +0800 [thread overview]
Message-ID: <202610290208.vMXHYOZa-lkp@intel.com> (raw)
In-Reply-To: <20261027150438.943354-1-bsdhenrymartin@gmail.com>
Hi Henry,
kernel test robot noticed the following build warnings:
[auto build test WARNING on manguebit/cifs-next]
[also build test WARNING on manguebit/cifs-fixes linus/master v7.3 next-20261027]
[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/Henry-Martin/cifs-fix-UAF-read-of-server-hostname-in-cifs_get_spnego_key/20261027-230438
base: https://git.manguebit.org/linux.git cifs-next
patch link: https://lore.kernel.org/r/20261027150438.943354-1-bsdhenrymartin%40gmail.com
patch subject: [PATCH] cifs: fix UAF read of server->hostname in cifs_get_spnego_key()
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20261029/202610290208.vMXHYOZa-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 16.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261029/202610290208.vMXHYOZa-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/202610290208.vMXHYOZa-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/smb/client/cifs_spnego.c: In function 'cifs_get_spnego_key':
>> fs/smb/client/cifs_spnego.c:199:1: warning: the frame size of 1304 bytes is larger than 1280 bytes [-Wframe-larger-than=]
199 | }
| ^
vim +199 fs/smb/client/cifs_spnego.c
f1d662a7d5e532 fs/cifs/cifs_spnego.c Steve French 2007-11-05 195
f1d662a7d5e532 fs/cifs/cifs_spnego.c Steve French 2007-11-05 196 out:
f1d662a7d5e532 fs/cifs/cifs_spnego.c Steve French 2007-11-05 197 kfree(description);
f1d662a7d5e532 fs/cifs/cifs_spnego.c Steve French 2007-11-05 198 return spnego_key;
f1d662a7d5e532 fs/cifs/cifs_spnego.c Steve French 2007-11-05 @199 }
b74cb9a80268be fs/cifs/cifs_spnego.c Sachin Prabhu 2016-05-17 200
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-10-28 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 15:04 Henry Martin
2026-10-28 18:58 ` kernel 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=202610290208.vMXHYOZa-lkp@intel.com \
--to=lkp@intel.com \
--cc=bharathsm@microsoft.com \
--cc=bsdhenrymartin@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=sprasad@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=tom@talpey.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®