Hi Qu, I checked with David, Seems like his github/repo.or.cz repo has latest dev patches before pushing them into kernel.org repo. -- With the help of 'git bisect', managed to debug this issue further. With this patch[1] applied we are running into this issue. https://asciinema.org/a/OMLXpd69iHaej0Xfsrr2ihKiP [1] btrfs: factor __btrfs_open_devices() to create btrfs_open_one_device() https://github.com/kdave/btrfs-devel/commit/25908a59bb5c54f896c646ed3a1f73b2727ad9b5 ---- Cheers, Lakshmipathi.G http://www.giis.co.in http://www.webminal.org On Fri, Nov 24, 2017 at 5:35 PM, Lakshmipathi.G <lakshmipathi.g@xxxxxxxxx> wrote: >>>> >>>> To make it clear, what kernel config and commit are you using when the >>>> test fails? >>>> >>> When I use attached kernel config along with tar from misc-next branch >>> (wget https://github.com/kdave/btrfs-devel/archive/misc-next.zip) this >>> issue happens. >> >> BTW, David seems to update his branch more often in his git.kernel.org >> branch than github. >> >> So it's possible that the branch from github is out dated. > > Okay, I didn't know that one, let me checkout his git.kernel.org branch and > check the results there. > >> >> For v4.14-rc7, even I enabled all the btrfs related configs, I still >> can't reproduce it. >> ------ >> $ zcat /proc/config.gz | grep BTRFS >> CONFIG_BTRFS_FS=m >> CONFIG_BTRFS_FS_POSIX_ACL=y >> CONFIG_BTRFS_FS_CHECK_INTEGRITY=y >> CONFIG_BTRFS_FS_RUN_SANITY_TESTS=y >> CONFIG_BTRFS_DEBUG=y >> CONFIG_BTRFS_ASSERT=y >> ------ >> >> So there is something strange happened. >> > > Yes. something strange going on. I use the same kernel config > for misc-next, 4.14 and 4.14.2 - issue happens only with > misc-next, as you mentioned it may not be up-to-date. > > > ---- > Cheers, > Lakshmipathi.G > http://www.giis.co.in http://www.webminal.org -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
