From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH v1 04/13] KVM: s390: move pv gmap functions into kvm
Date: Sat, 11 Jan 2025 02:42:11 +0800 [thread overview]
Message-ID: <202501110214.sqdsgfNV-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250108181451.74383-5-imbrenda@linux.ibm.com>
References: <20250108181451.74383-5-imbrenda@linux.ibm.com>
TO: Claudio Imbrenda <imbrenda@linux.ibm.com>
TO: kvm@vger.kernel.org
CC: linux-s390@vger.kernel.org
CC: frankja@linux.ibm.com
CC: borntraeger@de.ibm.com
CC: schlameuss@linux.ibm.com
CC: david@redhat.com
CC: willy@infradead.org
CC: hca@linux.ibm.com
CC: svens@linux.ibm.com
CC: agordeev@linux.ibm.com
CC: gor@linux.ibm.com
CC: nrb@linux.ibm.com
CC: nsg@linux.ibm.com
Hi Claudio,
kernel test robot noticed the following build warnings:
[auto build test WARNING on s390/features]
[also build test WARNING on kvm/queue kvm/next mst-vhost/linux-next linus/master v6.13-rc6 next-20250110]
[cannot apply to kvms390/next kvm/linux-next]
[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/Claudio-Imbrenda/KVM-s390-wrapper-for-KVM_BUG/20250109-021808
base: https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git features
patch link: https://lore.kernel.org/r/20250108181451.74383-5-imbrenda%40linux.ibm.com
patch subject: [PATCH v1 04/13] KVM: s390: move pv gmap functions into kvm
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: s390-randconfig-r071-20250110 (https://download.01.org/0day-ci/archive/20250111/202501110214.sqdsgfNV-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202501110214.sqdsgfNV-lkp@intel.com/
smatch warnings:
arch/s390/kernel/uv.c:302 uv_wiggle_folio() warn: missing error code? 'rc'
vim +/rc +302 arch/s390/kernel/uv.c
214d9bbcd3a672 Claudio Imbrenda 2020-01-21 280
72b1daff2671ce Claudio Imbrenda 2022-06-28 281 /**
0fab98cab07bbe Claudio Imbrenda 2025-01-08 282 * uv_wiggle_folio() - try to drain extra references to a folio
0fab98cab07bbe Claudio Imbrenda 2025-01-08 283 * @folio: the folio
0fab98cab07bbe Claudio Imbrenda 2025-01-08 284 * @split: whether to split a large folio
72b1daff2671ce Claudio Imbrenda 2022-06-28 285 *
0fab98cab07bbe Claudio Imbrenda 2025-01-08 286 * Context: Must be called while holding an extra reference to the folio;
0fab98cab07bbe Claudio Imbrenda 2025-01-08 287 * the mm lock should not be held.
68ad4743beaa71 David Hildenbrand 2024-05-08 288 */
0fab98cab07bbe Claudio Imbrenda 2025-01-08 289 int uv_wiggle_folio(struct folio *folio, bool split)
68ad4743beaa71 David Hildenbrand 2024-05-08 290 {
214d9bbcd3a672 Claudio Imbrenda 2020-01-21 291 int rc;
214d9bbcd3a672 Claudio Imbrenda 2020-01-21 292
0fab98cab07bbe Claudio Imbrenda 2025-01-08 293 folio_wait_writeback(folio);
0fab98cab07bbe Claudio Imbrenda 2025-01-08 294 if (split) {
eef88fe45ac978 David Hildenbrand 2024-05-08 295 folio_lock(folio);
eef88fe45ac978 David Hildenbrand 2024-05-08 296 rc = split_folio(folio);
eef88fe45ac978 David Hildenbrand 2024-05-08 297 folio_unlock(folio);
eef88fe45ac978 David Hildenbrand 2024-05-08 298
0fab98cab07bbe Claudio Imbrenda 2025-01-08 299 if (rc == -EBUSY)
eef88fe45ac978 David Hildenbrand 2024-05-08 300 return -EAGAIN;
0fab98cab07bbe Claudio Imbrenda 2025-01-08 301 if (rc != -EAGAIN)
214d9bbcd3a672 Claudio Imbrenda 2020-01-21 @302 return rc;
214d9bbcd3a672 Claudio Imbrenda 2020-01-21 303 }
0fab98cab07bbe Claudio Imbrenda 2025-01-08 304 lru_add_drain_all();
0fab98cab07bbe Claudio Imbrenda 2025-01-08 305 return -EAGAIN;
a52c25848e3143 Claudio Imbrenda 2022-06-28 306 }
0fab98cab07bbe Claudio Imbrenda 2025-01-08 307 EXPORT_SYMBOL_GPL(uv_wiggle_folio);
a52c25848e3143 Claudio Imbrenda 2022-06-28 308
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-01-10 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 18:42 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-08 18:14 [PATCH v1 00/13] KVM: s390: Stop using page->index and other things Claudio Imbrenda
2025-01-08 18:14 ` [PATCH v1 04/13] KVM: s390: move pv gmap functions into kvm Claudio Imbrenda
2025-01-09 17:42 ` kernel test robot
2025-01-15 12:48 ` Janosch Frank
2025-01-15 12:59 ` Claudio Imbrenda
2025-01-15 13:23 ` Janosch Frank
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=202501110214.sqdsgfNV-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.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.