On Sat, Aug 15, 2015 at 1:58 AM, Christoph Hellwig <hch@xxxxxx> wrote: > On Fri, Aug 14, 2015 at 05:52:44PM -0700, Duc Dang wrote: >> The commit 08439fec26 "ext4: remove block_device_ejected" only causes >> issue with ext4 and >> trying reverting it helps our test passes with ext4. >> >> But how about the same issue with ext2/ext3? > > I tried to fix the underlying issue, but I either failed to fully > fixed it or someone regressed it. > > Can you if rev 08439fec26 on it's own works to see if I missed > a case or it was regressed later? For more information. We tested kernel at commit 5f80f62ada "ext4: remove useless condition in if statement." (right before your commit) and still saw the issue. df3305156f989339529b3d6744b898d498fb1f7b [media] v4l: xilinx: Add Xilinx Video IP core 08439fec266c3cc5702953b4f54bdf5649357de0 ext4: remove block_device_ejected 5f80f62adae2a2920781a847805d34b36b323f7d ext4: remove useless condition in if statement. c9bca8b33118573da9b7ac2ea21947a8e4d287dd [media] v4l: of: Add v4l2_of_parse_link() function Further more, the issue does not happen with 3.19-rc7 but happens with 4.00-rc1 -- Regards, Duc Dang. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
