On Sat, Feb 24, 2018 at 10:07:33PM +0800, Anand Jain wrote:
> >> IP: btrfs_destroy_dev_replace_tgtdev+0x43/0xf0 [btrfs]
> >> Call Trace:
> >> btrfs_dev_replace_cancel+0x15f/0x180 [btrfs]
> >> btrfs_ioctl+0x2216/0x2590 [btrfs]
> >> do_vfs_ioctl+0x625/0x650
> >> SyS_ioctl+0x4e/0x80
> >>
On 02/24/2018 06:55 AM, David Sterba wrote:
On Tue, Feb 20, 2018 at 10:46:25PM +0800, Anand Jain wrote:
The replace target device can be missing in which case we don't
allocate a missing btrfs_device when mounted with the -o degraded.
So check the device before access.
BUG: unable to handle
On Tue, Feb 20, 2018 at 10:46:25PM +0800, Anand Jain wrote:
> The replace target device can be missing in which case we don't
> allocate a missing btrfs_device when mounted with the -o degraded.
> So check the device before access.
>
> BUG: unable to handle kernel NULL pointer dereference at
The replace target device can be missing in which case we don't
allocate a missing btrfs_device when mounted with the -o degraded.
So check the device before access.
BUG: unable to handle kernel NULL pointer dereference at 00b0
IP: btrfs_destroy_dev_replace_tgtdev+0x43/0xf0 [btrfs]
