dm commits marked Cc: stable but missing from 4.1

dm commits marked Cc: stable but missing from 4.1

[Eric Wheeler]

Hello all,

The following have been marked stable since December (dm-4.4-fixes-2) or 
so but still need pulled into the stable 4.1.y:

ed8b45a3679eb49069b094c0711b30833f27c734 dm btree: fix bufio buffer leaks in dm_btree_del() error path
50dd842ad83b43bed71790efb31cfb2f6c05c9c1 dm space map metadata: fix ref counting bug when bootstrapping a new space map
49e99fc717f624aa75ca755d6e7bc029efd3f0e9 dm thin metadata: fix bug when taking a metadata snapshot
30ce6e1cc5a0f781d60227e9096c86e188d2c2bd dm btree: fix leak of bufio-backed block in btree_split_sibling error path
172c238612ebf81cabccc86b788c9209af591f61 dm thin: restore requested 'error_if_no_space' setting on OODS to WRITE transition
ad5f498f610fa3fd8bd265139098bc1405cd2783 dm: initialize non-blk-mq queue data before queue is used

These patches cherry-pick cleanly into 4.1.18 in the order listed above.

Can these be queued for inclusion?

-Eric


--
Eric Wheeler, President           eWheeler, Inc. dba Global Linux Security
888-LINUX26 (888-546-8926)        Fax: 503-716-3878           PO Box 25107
www.GlobalLinuxSecurity.pro       Linux since 1996!     Portland, OR 97298

Re: dm commits marked Cc: stable but missing from 4.1

[Eric Wheeler]

On Mon, 29 Feb 2016, Eric Wheeler wrote:

> Hello all,
> 
> The following have been marked stable since December (dm-4.4-fixes-2) or 
> so but still need pulled into the stable 4.1.y:
> 
> ed8b45a3679eb49069b094c0711b30833f27c734 dm btree: fix bufio buffer leaks in dm_btree_del() error path
> 50dd842ad83b43bed71790efb31cfb2f6c05c9c1 dm space map metadata: fix ref counting bug when bootstrapping a new space map
> 49e99fc717f624aa75ca755d6e7bc029efd3f0e9 dm thin metadata: fix bug when taking a metadata snapshot
> 30ce6e1cc5a0f781d60227e9096c86e188d2c2bd dm btree: fix leak of bufio-backed block in btree_split_sibling error path
> 172c238612ebf81cabccc86b788c9209af591f61 dm thin: restore requested 'error_if_no_space' setting on OODS to WRITE transition
> ad5f498f610fa3fd8bd265139098bc1405cd2783 dm: initialize non-blk-mq queue data before queue is used
> 
> These patches cherry-pick cleanly into 4.1.18 in the order listed above.
> 
> Can these be queued for inclusion?

bump.

Can these be queued for 4.1.20?

-Eric