All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Shankari Anand <shankari.ak0208@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-scsi@vger.kernel.org>,
	<James.Bottomley@hansenpartnership.com>,
	<martin.petersen@oracle.com>,
	Shankari Anand <shankari.ak0208@gmail.com>,
	<oliver.sang@intel.com>
Subject: Re: [PATCH] scsi: sysfs: replace scnprintf() with sysfs_emit() in sdev_show_blacklist()
Date: Wed, 2 Jul 2025 14:41:53 +0800	[thread overview]
Message-ID: <202507020840.90a6d3bd-lkp@intel.com> (raw)
In-Reply-To: <20250620105344.455283-1-shankari.ak0208@gmail.com>


Hello,

kernel test robot noticed "blktests.scsi/005.fail" on:

commit: 2f688d0bc23ecf97b4f5255343dc891b196d1360 ("[PATCH] scsi: sysfs: replace scnprintf() with sysfs_emit() in sdev_show_blacklist()")
url: https://github.com/intel-lab-lkp/linux/commits/Shankari-Anand/scsi-sysfs-replace-scnprintf-with-sysfs_emit-in-sdev_show_blacklist/20250620-190212
base: https://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git for-next
patch link: https://lore.kernel.org/all/20250620105344.455283-1-shankari.ak0208@gmail.com/
patch subject: [PATCH] scsi: sysfs: replace scnprintf() with sysfs_emit() in sdev_show_blacklist()

in testcase: blktests
version: blktests-x86_64-55d3d61-1_20250617
with following parameters:

	disk: 1HDD
	test: scsi-005


config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) with 32G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)


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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202507020840.90a6d3bd-lkp@intel.com

2025-06-30 16:29:51 echo scsi/005
2025-06-30 16:29:51 ./check scsi/005
scsi/005 (test SCSI device blacklisting)                    
scsi/005 (test SCSI device blacklisting)                     [failed]
    runtime    ...  6.188s
    --- tests/scsi/005.out	2025-06-17 17:08:29.000000000 +0000
    +++ /lkp/benchmarks/blktests/results/nodev/scsi/005.out.bad	2025-06-30 16:29:58.087863341 +0000
    @@ -1,7 +1,7 @@
     Running scsi/005
                               
     AAAAAAAA BBBBBBBBBBBBBBBB 
    -HITACHI  OPEN-V           REPORTLUN2 TRY_VPD_PAGES
    +HITACHI  OPEN-V           REPORTLUN2
              Scanner          NOLUN
     Inateck                   
    ...
    (Run 'diff -u tests/scsi/005.out /lkp/benchmarks/blktests/results/nodev/scsi/005.out.bad' to see the entire diff)



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250702/202507020840.90a6d3bd-lkp@intel.com



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


      parent reply	other threads:[~2025-07-02  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 10:53 [PATCH] scsi: sysfs: replace scnprintf() with sysfs_emit() in sdev_show_blacklist() Shankari Anand
2025-06-27  5:49 ` Shankari Anand
2025-06-27 20:53 ` Bart Van Assche
2025-07-02  6:41 ` 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=202507020840.90a6d3bd-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=martin.petersen@oracle.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=shankari.ak0208@gmail.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.