Re: [PATCH] Btrfs: fix loss of prealloc extents past i_size after fsync log replay

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: c71bf099abdd Btrfs: Avoid orphan inodes cleanup while replaying log. The bot has also determined it's probably a bug fixing patch. (score: 6.2138) The bot has tested the

Re: [PATCH] btrfs: Fix possible softlock on single core machines

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 6d74119f1a3e Btrfs: avoid taking the chunk_mutex in do_chunk_alloc. The bot has also determined it's probably a bug fixing patch. (score: 55.2868) The bot has tested the

Re: [PATCH 08/16] btrfs: add sanity check when resuming balance after mount

Hi, [This is an automated email] This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 16.7330) The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126. v4.16: Build OK! v4.15.15:

Re: [PATCH] bitmap: fix memset optimization on big-endian systems

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 2a98dc028f91 include/linux/bitmap.h: turn bitmap_set and bitmap_clear into memset when possible. The bot has also determined it's probably a bug fixing patch. (score: 65.4067)

Re: [PATCH 07/16] btrfs: add proper safety check before resuming dev-replace

Hi, [This is an automated email] This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 34.4419) The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126. v4.16: Build OK! v4.15.15:

Re: [PATCH v2] Btrfs: fix NULL pointer dereference in log_dir_items

On Thu, Apr 05, 2018 at 07:11:14PM +0200, David Sterba wrote: >On Thu, Apr 05, 2018 at 04:42:34PM +0000, Sasha Levin wrote: >> Hi. >> >> [This is an automated email] >> >> This commit has been processed by the -stable helper bot and determined >> to be a

Re: [PATCH v2] Btrfs: fix NULL pointer dereference in log_dir_items

Hi. [This is an automated email] This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 9.9156) The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126, v4.15.15: Build OK! v4.14.32: Build OK!

Re: Please add 9c4f61f01d269815bb7c37be3ede59c5587747c6 to stable

On 04/23/2015 02:34 PM, Sasha Levin wrote: On 04/23/2015 02:24 PM, Josh Boyer wrote: On Thu, Apr 23, 2015 at 2:16 PM, Rich Freeman r-bt...@thefreemanclan.net wrote: On Mon, Apr 13, 2015 at 12:58 PM, Greg KH gre...@linuxfoundation.org wrote: On Mon, Apr 13, 2015 at 07:28:38PM +0500, Roman

Re: Please add 9c4f61f01d269815bb7c37be3ede59c5587747c6 to stable

On 04/23/2015 02:24 PM, Josh Boyer wrote: On Thu, Apr 23, 2015 at 2:16 PM, Rich Freeman r-bt...@thefreemanclan.net wrote: On Mon, Apr 13, 2015 at 12:58 PM, Greg KH gre...@linuxfoundation.org wrote: On Mon, Apr 13, 2015 at 07:28:38PM +0500, Roman Mamedov wrote: On Thu, 2 Apr 2015

Re: btrfs: kernel BUG at fs/btrfs/extent_io.c:676!

On 10/14/2014 02:31 AM, Chris Mason wrote: On Sun, Oct 12, 2014 at 10:15 PM, Sasha Levin sasha.le...@oracle.com wrote: Ping? This BUG_ON()ing due to GFP_ATOMIC allocation failure is really silly :( Agreed, I have a patch for this in testing. It didn't make my first pull but I'll get

Re: btrfs: kernel BUG at fs/btrfs/extent_io.c:676!

Ping? This BUG_ON()ing due to GFP_ATOMIC allocation failure is really silly :( On 03/23/2014 09:26 PM, Sasha Levin wrote: Hi all, While fuzzing with trinity inside KVM tools guest running latest -next kernel I've stumbled on the following spew. This is a result of a failed allocation

btrfs: hang on boot due to tests

Hi all, It seems that some recent changes to btrfs tests make it hang during boot: [ 49.730033] NMI watchdog: BUG: soft lockup - CPU#34 stuck for 23s! [swapper/0:1] [ 49.730033] Modules linked in: [ 49.730033] hardirqs last enabled at (6389143): restore_args

Re: btrfs: hang on boot due to tests

On 06/09/2014 11:59 AM, Chris Mason wrote: On 06/09/2014 11:16 AM, Sasha Levin wrote: Hi all, It seems that some recent changes to btrfs tests make it hang during boot: [ 49.730033] NMI watchdog: BUG: soft lockup - CPU#34 stuck for 23s! [swapper/0:1] [ 49.730033] Modules

Re: btrfs: lock inversion between delayed_node-mutex and found-groups_sem

On 04/07/2014 01:17 PM, Chris Mason wrote: On 04/07/2014 12:54 PM, David Sterba wrote: On Fri, Apr 04, 2014 at 05:15:23PM -0400, Sasha Levin wrote: On 03/26/2014 01:01 PM, Jeff Mahoney wrote: On 3/17/14, 9:05 AM, David Sterba wrote: On Fri, Mar 14, 2014 at 08:12:16PM -0400, Sasha Levin

Re: btrfs: lock inversion between delayed_node-mutex and found-groups_sem

On 03/26/2014 01:01 PM, Jeff Mahoney wrote: On 3/17/14, 9:05 AM, David Sterba wrote: On Fri, Mar 14, 2014 at 08:12:16PM -0400, Sasha Levin wrote: While fuzzing with trinity inside a KVM tools guest running the latest -next kernel I've stumbled on the following: [ 788.458756]CPU0

btrfs: kernel BUG at fs/btrfs/extent_io.c:676!

Hi all, While fuzzing with trinity inside KVM tools guest running latest -next kernel I've stumbled on the following spew. This is a result of a failed allocation in alloc_extent_state_atomic() which triggers a BUG_ON when the return value is NULL. It's a bit weird that it BUGs on failed

btrfs: lock inversion between delayed_node-mutex and found-groups_sem

Hi all, While fuzzing with trinity inside a KVM tools guest running the latest -next kernel I've stumbled on the following: [ 788.451695] = [ 788.452455] [ INFO: possible irq lock inversion dependency detected ] [ 788.453020]