Re: Btrfs stable updates for 4.0
On Fri, Jun 19, 2015 at 01:31:31PM -0700, Greg KH wrote: 5cc2b17e80cf5770f2e585c2d90fd8af1b901258 # 3.14+ Does not build on 3.14+, sorry. Please provide a backported version if you want to see it there. I'm sorry about the hassle with applying to older version. My main goal is to provide a set of patches for the latest stable series, and they get reviewed and tested properly. I try to look whether the patches are relvant for older versions but this takes extra time. I don't have particular interest in these so it's only best effort, but so far it hasn't met the 'best' premise. I'll try better next time. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Btrfs stable updates for 4.0
On Thu, Jun 25, 2015 at 05:10:29PM +0200, David Sterba wrote: On Fri, Jun 19, 2015 at 01:31:31PM -0700, Greg KH wrote: 5cc2b17e80cf5770f2e585c2d90fd8af1b901258 # 3.14+ Does not build on 3.14+, sorry. Please provide a backported version if you want to see it there. I'm sorry about the hassle with applying to older version. My main goal is to provide a set of patches for the latest stable series, and they get reviewed and tested properly. I try to look whether the patches are relvant for older versions but this takes extra time. I don't have particular interest in these so it's only best effort, but so far it hasn't met the 'best' premise. I'll try better next time. That's fine, no need to work hard for any longterm kernel if you don't want to, just letting you know that this patch didn't work there. I don't care if it doesn't make it if you don't :) thanks, greg k-h -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Btrfs stable updates for 4.0
On Thu, Jun 11, 2015 at 06:06:32PM +0200, David Sterba wrote: Hi, please queue the following patches to 4.0 stable. There are fixes for user visible bugs and one usability regression with RAID1 - single conversion during balance. One of the patches does not apply cleanly to 4.0.5, there's a minor conflict in patch context (153c35b60c72de9fae06c8e2c8b2c47d79d4, the last one). A reply to this mail is the adapted version or you can pull/cherry-pick from git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-stable-4.0 Subjects: Btrfs: send, add missing check for dead clone root Btrfs: send, don't leave without decrementing clone root's send_progress btrfs: incorrect handling for fiemap_fill_next_extent return btrfs: cleanup orphans while looking up default subvolume Btrfs: fix range cloning when same inode used as source and destination Btrfs: fix uninit variable in clone ioctl Btrfs: fix regression in raid level conversion Commits: 5cc2b17e80cf5770f2e585c2d90fd8af1b901258 # 3.14+ Does not build on 3.14+, sorry. Please provide a backported version if you want to see it there. greg k-h -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in
Re: Btrfs stable updates for 4.0
On Thu, Jun 11, 2015 at 06:06:32PM +0200, David Sterba wrote: Hi, please queue the following patches to 4.0 stable. There are fixes for user visible bugs and one usability regression with RAID1 - single conversion during balance. One of the patches does not apply cleanly to 4.0.5, there's a minor conflict in patch context (153c35b60c72de9fae06c8e2c8b2c47d79d4, the last one). A reply to this mail is the adapted version or you can pull/cherry-pick from git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-stable-4.0 Subjects: Btrfs: send, add missing check for dead clone root Btrfs: send, don't leave without decrementing clone root's send_progress btrfs: incorrect handling for fiemap_fill_next_extent return btrfs: cleanup orphans while looking up default subvolume Btrfs: fix range cloning when same inode used as source and destination Btrfs: fix uninit variable in clone ioctl Btrfs: fix regression in raid level conversion Commits: 5cc2b17e80cf5770f2e585c2d90fd8af1b901258 # 3.14+ 2f1f465ae6da244099af55c066e5355abd8ff620 # 3.14+ Because 5cc2b17e80cf5770f2e585c2d90fd8af1b901258 breaks the build, 2f1f465ae6da244099af55c066e5355abd8ff620 does not apply to 3.14 either :( -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in
Re: Btrfs stable updates for 4.0
On Thu, Jun 11, 2015 at 06:06:32PM +0200, David Sterba wrote: Hi, please queue the following patches to 4.0 stable. There are fixes for user visible bugs and one usability regression with RAID1 - single conversion during balance. One of the patches does not apply cleanly to 4.0.5, there's a minor conflict in patch context (153c35b60c72de9fae06c8e2c8b2c47d79d4, the last one). A reply to this mail is the adapted version or you can pull/cherry-pick from git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-stable-4.0 Subjects: Btrfs: send, add missing check for dead clone root Btrfs: send, don't leave without decrementing clone root's send_progress btrfs: incorrect handling for fiemap_fill_next_extent return btrfs: cleanup orphans while looking up default subvolume Btrfs: fix range cloning when same inode used as source and destination Btrfs: fix uninit variable in clone ioctl Btrfs: fix regression in raid level conversion Commits: 5cc2b17e80cf5770f2e585c2d90fd8af1b901258 # 3.14+ 2f1f465ae6da244099af55c066e5355abd8ff620 # 3.14+ 26e726afe01c1c82072cf23a5ed89ce25f39d9f2 # 3.10+ 727b9784b6085c99c2f836bf4fcc2848dc9cf904 # 3.14+ Thanks, I'm applying the above commits to 3.16 kernel as well. Cheers, -- Luís df858e76723ace61342b118aa4302bd09de4e386 # 4.0+ de249e66a73d69281cd812087979c6fae552 # 4.0+ 153c35b60c72de9fae06c8e2c8b2c47d79d4 # 4.0+ Thanks. -- To unsubscribe from this list: send the line unsubscribe stable in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Btrfs stable updates for 4.0
Hi, please queue the following patches to 4.0 stable. There are fixes for user visible bugs and one usability regression with RAID1 - single conversion during balance. One of the patches does not apply cleanly to 4.0.5, there's a minor conflict in patch context (153c35b60c72de9fae06c8e2c8b2c47d79d4, the last one). A reply to this mail is the adapted version or you can pull/cherry-pick from git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-stable-4.0 Subjects: Btrfs: send, add missing check for dead clone root Btrfs: send, don't leave without decrementing clone root's send_progress btrfs: incorrect handling for fiemap_fill_next_extent return btrfs: cleanup orphans while looking up default subvolume Btrfs: fix range cloning when same inode used as source and destination Btrfs: fix uninit variable in clone ioctl Btrfs: fix regression in raid level conversion Commits: 5cc2b17e80cf5770f2e585c2d90fd8af1b901258 # 3.14+ 2f1f465ae6da244099af55c066e5355abd8ff620 # 3.14+ 26e726afe01c1c82072cf23a5ed89ce25f39d9f2 # 3.10+ 727b9784b6085c99c2f836bf4fcc2848dc9cf904 # 3.14+ df858e76723ace61342b118aa4302bd09de4e386 # 4.0+ de249e66a73d69281cd812087979c6fae552 # 4.0+ 153c35b60c72de9fae06c8e2c8b2c47d79d4 # 4.0+ Thanks. -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
