Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:rxrpc-fixes 3/3] net/rxrpc/conn_event.c:254:10: warning: variable 'ret' is uninitialized when used here
Date: Tue, 12 May 2026 08:59:50 +0800	[thread overview]
Message-ID: <202605120837.hzpSAALd-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git rxrpc-fixes
head:   e9d335dc719f98e1964c57fd1f5f92b6fd1c0c52
commit: e9d335dc719f98e1964c57fd1f5f92b6fd1c0c52 [3/3] rxrpc: Fix RESPONSE packet verification to extract skb to a linear buffer
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260512/202605120837.hzpSAALd-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260512/202605120837.hzpSAALd-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/202605120837.hzpSAALd-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> net/rxrpc/conn_event.c:254:10: warning: variable 'ret' is uninitialized when used here [-Wuninitialized]
     254 |                 return ret;
         |                        ^~~
   net/rxrpc/conn_event.c:250:9: note: initialize the variable 'ret' to silence this warning
     250 |         int ret;
         |                ^
         |                 = 0
   1 warning generated.


vim +/ret +254 net/rxrpc/conn_event.c

   242	
   243	static int rxrpc_verify_response(struct rxrpc_connection *conn,
   244					 struct sk_buff *skb)
   245	{
   246		struct xdr_buffer response = {
   247			.len = skb->len - sizeof(struct rxrpc_wire_header),
   248		};
   249		void *buffer;
   250		int ret;
   251	
   252		buffer = kmalloc(response.len, GFP_NOFS);
   253		if (!buffer)
 > 254			return ret;
   255	
   256		ret = skb_copy_bits(skb, sizeof(struct rxrpc_wire_header), buffer, response.len);
   257		if (ret < 0)
   258			goto out;
   259	
   260		response.p = buffer;
   261		ret = conn->security->verify_response(conn, skb, &response);
   262	
   263	out:
   264		kfree(buffer);
   265		return ret;
   266	}
   267	

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

                 reply	other threads:[~2026-05-12  1:00 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=202605120837.hzpSAALd-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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