| 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
| ||
|
Date: Mon, 15 Nov 2010 16:34:44 -0500 From: Mike Snitzer <snitzer@...hat.com> To: jaxboe@...ionio.com Cc: device-mapper development <dm-devel@...hat.com>, "Jun'ichi Nomura" <j-nomura@...jp.nec.com>, Alasdair G Kergon <agk@...hat.com>, Li Zefan <lizf@...fujitsu.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2] block: rename trace_block_remap to trace_block_bio_remap On Mon, Nov 15 2010 at 3:58pm -0500, Mike Snitzer <snitzer@...hat.com> wrote: > Hi Jens, > > This may have slipped through while you were traveling? > > Patch is also available here: > https://patchwork.kernel.org/patch/300552/ > > Not sure if this change is concerning on a kABI level? To be clear: that concern/question was prompted from having taken a quick glance at lwn's kernel summit "KS2010: ABI status for tracepoints" coverage: http://lwn.net/Articles/412685/ But in that article it clearly states: "there are to be no stable tracepoints in drivers or filesystems". Not sure where that leaves tracepoints for the block layer. Anyway, seems tracepoint kABI is likely a concern for the future (not the immediate future). So this change would be nice to get in before there is a new tracepoint kABI-aware sheriff in town. Mike -- 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/
Powered by blists - more mailing lists