Re: [PATCH v2] Btrfs: fix range cloning when same inode used as source and destination

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 02 Apr 2015 18:25:11 +0100, Filipe Manana wrote:

> V2: Fixed a warning about potentially uninitialized variable. David
>     got this warning on a 4.5.1 gcc, but I didn't on a 4.9.2 gcc
>     however.

I was *just* about to post this warning, since I saw it only a minute ago!

I assume you mean:

fs/btrfs/ioctl.c: In function 'btrfs_clone':
fs/btrfs/ioctl.c:3531:14: warning: 'next_key_min_offset' may be used uninitialized in this function [-Wmaybe-uninitialized]
   key.offset = next_key_min_offset;
              ^

..and this is with 4.9.2 here.

Anyway..thanks for being faster :)

Holger

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux