linux-kernel - xen_biovec_phys_mergeable not exported

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 20 Sep 2011 14:25:53 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	linux-kernel@...r.kernel.org
Cc:	Jens Axboe <jaxboe@...ionio.com>
Subject: xen_biovec_phys_mergeable not exported

In my NVMe driver, I call BIOVEC_PHYS_MERGEABLE().  If CONFIG_XEN
is defined, it references xen_biovec_phys_mergeable() which is not
EXPORT_SYMBOL.  I think BIOVEC_PHYS_MERGABLE is a perfectly kosher thing
to be calling from a module that implements a bio-based block driver,
so I think the right thing to do is to add an EXPORT_SYMBOL(_GPL?) to
the Xen code when I submit the driver.

Does anyone have a different opinion on this?

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/