On 09/01/2014 01:15 PM, Boaz Harrosh wrote: > On 08/27/2014 06:22 PM, Boaz Harrosh wrote: >> Jens Hi >> >> What do you intend to do with these fixes? These are real bugs on devices >> shipped for a while now. I think they need to go into current 3.17-rcX Kernel. >> > > Jens hi > > I have seen that the brd patch went into rc3. > > I should insist then, that these patches go into this rc cycle ASAP. > For one they fix real *hard* unexpected bugs with brd that make it trash data. > > But specially because the patch to brd that just went into Kernel introduces > a wrong module parameter "show_part" which must be removed. If we release a Kernel > with it, it will be pain, we will need to deprecate it which is long and annoying > procedure. It is wrong because it must be always on. Pleas see below > > This patchset is based on what just went into Kernel. > Also on git here: git://git.open-osd.org/pmem.git brd-partitions branch > > [http://git.open-osd.org/gitweb.cgi?p=pmem.git;a=shortlog;h=refs/heads/brd-partitions] > > Thanks > Boaz > <> >> list of patches: >> [PATCH 1/5] axonram: Fix bug in direct_access >> [PATCH 2/5] Change direct_access calling convention <> >> [PATCH 3/5] brd: Add getgeo to block ops <> >> [PATCH 4/5] brd: Fix all partitions BUGs >> [PATCH 5/5] brd: Request from fdisk 4k alignment Ping Jens? Please tell me what you want to do with these patches. They must go into this Kernel cycle before brd is released with wrong user-mode visible nub If you want you can drop the [PATCH 3/5] which is not important and can go in next cycle, but the others are real BUG fixes. Thanks Boaz -- 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
