linux-kernel - Re: Unexport of blk_get_queue and blk_put

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080421122413.GD6011@cs181133002.pp.htv.fi>
Date:	Mon, 21 Apr 2008 15:24:13 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Bart Van Assche <bart.vanassche@...il.com>
Cc:	Philipp Reisner <philipp.reisner@...bit.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Unexport of blk_get_queue and blk_put_queue

On Fri, Apr 18, 2008 at 01:43:17PM +0200, Bart Van Assche wrote:
> Hello Adrian,

Hi Bart,

> I noticed that blk_get_queue and blk_put_queue were unexported in the
> 2.6.25 kernel. Are you aware that this breaks DRBD (an out-of-tree
> kernel module) ?

no, I verify that my patches don't break Linus' tree and often also peek 
at -mm, but not at external modules.

And I'm a proponent of "no stable kernel API, but as many external 
modules as reasonably possible should be part of the kernel", so emails 
like yours are always a good point to start asking why the code isn't in 
Linus' tree.

What happened to DRBD?
It didn't seem that far from getting merged half a year ago.

> Bart.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
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/