On Thu, Jun 11, 2015 at 4:27 PM, David Miller wrote:
> From: sfel...@gmail.com
> Date: Thu, 11 Jun 2015 11:20:42 -0700
>
>> From: Scott Feldman
>>
>> This particular BUG_ON condition was checking for attr set err in the
>> COMMIT phase, which isn't expected (it's a driver bug if PREPARE phase is
From: sfel...@gmail.com
Date: Thu, 11 Jun 2015 11:20:42 -0700
> From: Scott Feldman
>
> This particular BUG_ON condition was checking for attr set err in the
> COMMIT phase, which isn't expected (it's a driver bug if PREPARE phase is
> OK but COMMIT fails). But BUG_ON() is too strong for this c
From: Scott Feldman
This particular BUG_ON condition was checking for attr set err in the
COMMIT phase, which isn't expected (it's a driver bug if PREPARE phase is
OK but COMMIT fails). But BUG_ON() is too strong for this case, so change
to WARN(). BUG_ON() would be warranted if the system was
