Re: [dm-devel] [PATCH stable] block: discard bdi_unregister() in favour of bdi_destroy()

On Wed, Apr 29, 2015 at 5:32 PM, NeilBrown wrote: > > bdi_unregister() now contains very little functionality. > > It contains a "WARN_ON" if bdi->dev is NULL. This warning is of no > real consequence as bdi->dev isn't needed by anything else in the function, > and it triggers if >blk_cleanup

Re: [PATCH stable] block: discard bdi_unregister() in favour of bdi_destroy()

On Thu, Apr 30, 2015 at 10:32:33AM +1000, NeilBrown wrote: > > bdi_unregister() now contains very little functionality. > > It contains a "WARN_ON" if bdi->dev is NULL. This warning is of no > real consequence as bdi->dev isn't needed by anything else in the function, > and it triggers if >b

[PATCH stable] block: discard bdi_unregister() in favour of bdi_destroy()

bdi_unregister() now contains very little functionality. It contains a "WARN_ON" if bdi->dev is NULL. This warning is of no real consequence as bdi->dev isn't needed by anything else in the function, and it triggers if blk_cleanup_queue() -> bdi_destroy() is called before bdi_unregister, whic