On Wed, Apr 02, 2014 at 12:17:58PM -0700, Zach Brown wrote:
> > +static int bio_integrity_generate_verify(struct bio *bio, int operate)
> > {
>
> > + if (operate)
> > + sector = bio->bi_iter.bi_sector;
> > + else
> > + sector = bio->bi_integrity->bip_iter.bi_sector;
>
> > + if (operate) {
> > + bi->generate_fn(&bix);
> > + } else {
> > + ret = bi->verify_fn(&bix);
> > + if (ret) {
> > + kunmap_atomic(kaddr);
> > + return ret;
> > + }
> > + }
>
> I was glad to see this replaced with explicit sector and func arguments
> in later refactoring in the 6/ patch.
>
> But I don't think the function poiner casts in that 6/ patch are wise
> (Or even safe all the time, given crazy function pointer trampolines?
> Is that still a thing?). I'd have made a single walk_fn type that
> returns and have the non-returning iterators just return 0.
Noted. I cleaned all that crap out just yesterday, so now there's only one
walk function and some context data that gets passed to the iterator function.
Much less horrifying.
(I really only included this patch so that I'd have less rebasing work when
3.15-rc1 comes out.)
--D
>
> - z
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>