From: kernel test robot <lkp@intel.com>
To: Valentine Sinitsyn <valesini@yandex-team.ru>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejun Heo <tj@kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2 2/2] PCI: implement custom llseek method for PCI resource entries in sysfs
Date: Tue, 22 Aug 2023 07:15:15 +0800 [thread overview]
Message-ID: <202308220648.wcmc5jWq-lkp@intel.com> (raw)
In-Reply-To: <20230821072956.114193-2-valesini@yandex-team.ru>
Hi Valentine,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.5-rc7 next-20230821]
[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/Valentine-Sinitsyn/PCI-implement-custom-llseek-method-for-PCI-resource-entries-in-sysfs/20230821-163118
base: linus/master
patch link: https://lore.kernel.org/r/20230821072956.114193-2-valesini%40yandex-team.ru
patch subject: [RESEND PATCH v2 2/2] PCI: implement custom llseek method for PCI resource entries in sysfs
config: powerpc-randconfig-r024-20230821 (https://download.01.org/0day-ci/archive/20230822/202308220648.wcmc5jWq-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230822/202308220648.wcmc5jWq-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/202308220648.wcmc5jWq-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/pci/pci-sysfs.c:936:13: warning: no previous prototype for 'pci_adjust_legacy_attr' [-Wmissing-prototypes]
936 | void __weak pci_adjust_legacy_attr(struct pci_bus *b,
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/pci/pci-sysfs.c: In function 'pci_create_legacy_files':
>> drivers/pci/pci-sysfs.c:971:32: error: 'pci_llseek_resource' undeclared (first use in this function); did you mean 'pci_claim_resource'?
971 | b->legacy_io->llseek = pci_llseek_resource;
| ^~~~~~~~~~~~~~~~~~~
| pci_claim_resource
drivers/pci/pci-sysfs.c:971:32: note: each undeclared identifier is reported only once for each function it appears in
vim +971 drivers/pci/pci-sysfs.c
940
941 /**
942 * pci_create_legacy_files - create legacy I/O port and memory files
943 * @b: bus to create files under
944 *
945 * Some platforms allow access to legacy I/O port and ISA memory space on
946 * a per-bus basis. This routine creates the files and ties them into
947 * their associated read, write and mmap files from pci-sysfs.c
948 *
949 * On error unwind, but don't propagate the error to the caller
950 * as it is ok to set up the PCI bus without these files.
951 */
952 void pci_create_legacy_files(struct pci_bus *b)
953 {
954 int error;
955
956 if (!sysfs_initialized)
957 return;
958
959 b->legacy_io = kcalloc(2, sizeof(struct bin_attribute),
960 GFP_ATOMIC);
961 if (!b->legacy_io)
962 goto kzalloc_err;
963
964 sysfs_bin_attr_init(b->legacy_io);
965 b->legacy_io->attr.name = "legacy_io";
966 b->legacy_io->size = 0xffff;
967 b->legacy_io->attr.mode = 0600;
968 b->legacy_io->read = pci_read_legacy_io;
969 b->legacy_io->write = pci_write_legacy_io;
970 /* See pci_create_attr() for motivation */
> 971 b->legacy_io->llseek = pci_llseek_resource;
972 b->legacy_io->mmap = pci_mmap_legacy_io;
973 b->legacy_io->f_mapping = iomem_get_mapping;
974 pci_adjust_legacy_attr(b, pci_mmap_io);
975 error = device_create_bin_file(&b->dev, b->legacy_io);
976 if (error)
977 goto legacy_io_err;
978
979 /* Allocated above after the legacy_io struct */
980 b->legacy_mem = b->legacy_io + 1;
981 sysfs_bin_attr_init(b->legacy_mem);
982 b->legacy_mem->attr.name = "legacy_mem";
983 b->legacy_mem->size = 1024*1024;
984 b->legacy_mem->attr.mode = 0600;
985 b->legacy_mem->mmap = pci_mmap_legacy_mem;
986 /* See pci_create_attr() for motivation */
987 b->legacy_io->llseek = pci_llseek_resource;
988 b->legacy_mem->f_mapping = iomem_get_mapping;
989 pci_adjust_legacy_attr(b, pci_mmap_mem);
990 error = device_create_bin_file(&b->dev, b->legacy_mem);
991 if (error)
992 goto legacy_mem_err;
993
994 return;
995
996 legacy_mem_err:
997 device_remove_bin_file(&b->dev, b->legacy_io);
998 legacy_io_err:
999 kfree(b->legacy_io);
1000 b->legacy_io = NULL;
1001 kzalloc_err:
1002 dev_warn(&b->dev, "could not create legacy I/O port and ISA memory resources in sysfs\n");
1003 }
1004
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-21 23:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 19:08 [PATCH] kernfs: implement custom llseek method to fix userspace regression Valentine Sinitsyn
2023-08-14 20:01 ` Dan Williams
2023-08-15 8:25 ` Valentin Sinitsyn
2023-08-15 15:48 ` Dan Williams
2023-08-17 18:53 ` Valentin Sinitsyn
2023-08-21 7:29 ` [RESEND PATCH v2 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-08-21 7:29 ` [RESEND PATCH v2 2/2] PCI: implement custom llseek method for PCI resource entries in sysfs Valentine Sinitsyn
2023-08-21 19:55 ` Bjorn Helgaas
2023-08-22 7:51 ` [PATCH v3 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-08-22 7:51 ` [PATCH v3 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-08-22 11:54 ` [PATCH v4 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-08-22 11:54 ` [PATCH v4 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-08-22 17:43 ` kernel test robot
2023-08-23 12:58 ` [PATCH v5 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-08-23 14:37 ` Greg Kroah-Hartman
2023-08-23 14:39 ` Greg Kroah-Hartman
2023-08-23 20:11 ` Valentin Sinitsyn
2023-08-23 12:58 ` [PATCH v5 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-08-25 14:10 ` kernel test robot
2023-08-28 7:22 ` Valentin Sinitsyn
2023-08-29 20:02 ` Bjorn Helgaas
2023-08-29 20:26 ` Bjorn Helgaas
2023-09-02 15:50 ` [PATCH v6 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-09-05 7:02 ` kernel test robot
2023-09-08 13:49 ` [PATCH v7 " Valentine Sinitsyn
2023-09-08 13:49 ` [PATCH v7 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-09-08 13:56 ` [PATCH v8 1/2] kernfs: sysfs: support custom llseek method for sysfs entries Valentine Sinitsyn
2023-09-08 13:56 ` [PATCH v8 2/2] PCI: Implement custom llseek for sysfs resource entries Valentine Sinitsyn
2023-09-02 15:50 ` [PATCH v6 " Valentine Sinitsyn
2023-08-21 23:15 ` kernel test robot [this message]
2023-08-22 8:09 ` [RESEND PATCH v2 2/2] PCI: implement custom llseek method for PCI resource entries in sysfs Valentin Sinitsyn
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=202308220648.wcmc5jWq-lkp@intel.com \
--to=lkp@intel.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tj@kernel.org \
--cc=valesini@yandex-team.ru \
/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