On Thu, Jan 29 2015 at 5:43pm -0500, Keith Busch <keith.busch@xxxxxxxxx> wrote: > On Wed, 28 Jan 2015, Jens Axboe wrote: > >On 01/28/2015 10:44 AM, Mike Snitzer wrote: > >>On Wed, Jan 28 2015 at 11:42am -0500, > >>Jens Axboe <axboe@xxxxxxxxx> wrote: > >>>I'd prefer to take these prep patches through the block tree. > >> > >>Great, should I send the patches or can you cherry-pick? > > > >I already cherry picked them, they are in the for-3.20/core branch. > > I might be getting ahead of myself for trying this right now (sorry if > that's the case) but 'for-3.20/core' is missing necessary parts of the > series and hits a BUG_ON at blk-core.c:2333. The original request is > initialized when setting up the clone, and in this branch, that happens > in prep_fn before the request was dequeued so it's not in the queuelist > when it started. > > One of my commits relocated the initialization, but I didn't realize it > had a hard dependency on the follow-on commit. Should we reorder that > part of the series? Which follow on commit are you referring to? Please be specific about which commits you think are out of order. Also, what are you testing... are you using the linux-dm.git tree's 'dm-for-3.20' branch which builds on Jens' 'for-3.20/core'? If not please test that and see if you still have problems (without the associated DM changes all the block preparation changes that Jens cherry-picked shouldn't cause any problems at all). -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
