All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [char-misc:char-misc-next 11/26] vmbus_bufring.c:172:37: warning: taking address of packed member of 'struct vmbus_bufring' may result in an unaligned pointer value
Date: Fri, 12 Apr 2024 19:19:37 +0800	[thread overview]
Message-ID: <202404121913.GhtSoKbW-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence bisect report"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Saurabh Sengar <ssengar@linux.microsoft.com>
CC: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
CC: Long Li <longli@microsoft.com>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-next
head:   dc806bd48abc1b8a4ae72709a37e65db42a32048
commit: 82b0945ce2c2d636d5e893ad50210875c929f257 [11/26] tools: hv: Add new fcopy application based on uio driver
:::::: branch date: 22 hours ago
:::::: commit date: 22 hours ago
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240412/202404121913.GhtSoKbW-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/r/202404121913.GhtSoKbW-lkp@intel.com/

All warnings (new ones prefixed by >>):

   vmbus_bufring.c: In function 'vmbus_txbr_write':
>> vmbus_bufring.c:172:37: warning: taking address of packed member of 'struct vmbus_bufring' may result in an unaligned pointer value [-Waddress-of-packed-member]
     172 |         while (!rte_atomic32_cmpset(&vbr->windex, old_windex, next_windex))
         |                                     ^~~~~~~~~~~~

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

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <yujie.liu@intel.com>
To: Saurabh Sengar <ssengar@linux.microsoft.com>
Cc: <oe-kbuild-all@lists.linux.dev>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Long Li <longli@microsoft.com>
Subject: [char-misc:char-misc-next 11/26] vmbus_bufring.c:172:37: warning: taking address of packed member of 'struct vmbus_bufring' may result in an unaligned pointer value
Date: Wed, 17 Apr 2024 12:01:15 +0800	[thread overview]
Message-ID: <202404121913.GhtSoKbW-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-next
head:   dc806bd48abc1b8a4ae72709a37e65db42a32048
commit: 82b0945ce2c2d636d5e893ad50210875c929f257 [11/26] tools: hv: Add new fcopy application based on uio driver
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0

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 <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202404121913.GhtSoKbW-lkp@intel.com/

All warnings (new ones prefixed by >>):

   vmbus_bufring.c: In function 'vmbus_txbr_write':
>> vmbus_bufring.c:172:37: warning: taking address of packed member of 'struct vmbus_bufring' may result in an unaligned pointer value [-Waddress-of-packed-member]
     172 |         while (!rte_atomic32_cmpset(&vbr->windex, old_windex, next_windex))
         |                                     ^~~~~~~~~~~~

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


             reply	other threads:[~2024-04-12 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 11:19 kernel test robot [this message]
2024-04-17  4:01 ` [char-misc:char-misc-next 11/26] vmbus_bufring.c:172:37: warning: taking address of packed member of 'struct vmbus_bufring' may result in an unaligned pointer value 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=202404121913.GhtSoKbW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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 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.