Re: [PATCH 1/7] Btrfs: replace BUG() with WARN_ONCE in raid56

2016-10-12 Thread Liu Bo
On Wed, Oct 12, 2016 at 05:06:55PM +0200, David Sterba wrote: > On Mon, May 16, 2016 at 10:32:48AM +0200, David Sterba wrote: > > On Sun, May 15, 2016 at 04:19:28PM +0200, Holger Hoffstätte wrote: > > > On 05/14/16 02:06, Liu Bo wrote: > > > > This BUG() has been triggered by a fuzz testing image,

Re: [PATCH 1/7] Btrfs: replace BUG() with WARN_ONCE in raid56

2016-10-12 Thread David Sterba
On Mon, May 16, 2016 at 10:32:48AM +0200, David Sterba wrote: > On Sun, May 15, 2016 at 04:19:28PM +0200, Holger Hoffstätte wrote: > > On 05/14/16 02:06, Liu Bo wrote: > > > This BUG() has been triggered by a fuzz testing image, but in fact > > > btrfs can handle this gracefully by returning -EIO.

Re: [PATCH 1/7] Btrfs: replace BUG() with WARN_ONCE in raid56

2016-05-16 Thread David Sterba
On Sun, May 15, 2016 at 04:19:28PM +0200, Holger Hoffstätte wrote: > On 05/14/16 02:06, Liu Bo wrote: > > This BUG() has been triggered by a fuzz testing image, but in fact > > btrfs can handle this gracefully by returning -EIO. > > > > Thus, use WARN_ONCE for warning purpose and don't leave a

Re: [PATCH 1/7] Btrfs: replace BUG() with WARN_ONCE in raid56

2016-05-15 Thread Holger Hoffstätte
On 05/14/16 02:06, Liu Bo wrote: > This BUG() has been triggered by a fuzz testing image, but in fact > btrfs can handle this gracefully by returning -EIO. > > Thus, use WARN_ONCE for warning purpose and don't leave a possible > kernel panic. > > Signed-off-by: Liu Bo >

Re: [PATCH 1/7] Btrfs: replace BUG() with WARN_ONCE in raid56

2016-05-14 Thread Qu Wenruo
On 05/14/2016 08:06 AM, Liu Bo wrote: This BUG() has been triggered by a fuzz testing image, but in fact btrfs can handle this gracefully by returning -EIO. Thus, use WARN_ONCE for warning purpose and don't leave a possible kernel panic. Signed-off-by: Liu Bo ---

[PATCH 1/7] Btrfs: replace BUG() with WARN_ONCE in raid56

2016-05-13 Thread Liu Bo
This BUG() has been triggered by a fuzz testing image, but in fact btrfs can handle this gracefully by returning -EIO. Thus, use WARN_ONCE for warning purpose and don't leave a possible kernel panic. Signed-off-by: Liu Bo --- fs/btrfs/raid56.c | 2 +- 1 file changed, 1