On Wed, May 2, 2012 at 4:54 PM, David Sterba <d...@jikos.cz> wrote: > > On Thu, Apr 19, 2012 at 05:42:05PM +0200, Marco L. Crociani wrote: > > Apr 19 17:38:41 evo kernel: [ 347.661915] Call Trace: > > Apr 19 17:38:41 evo kernel: [ 347.661964] [<ffffffffa00b76ac>] > > > btrfs_ioctl_dev_info+0x15c/0x1a0 [btrfs] > > Apr 19 17:38:41 evo kernel: [ 347.662013] [<ffffffffa00ba9b1>] > > > btrfs_ioctl+0x571/0x6c0 [btrfs] > > Apr 19 17:38:41 evo kernel: [ 347.662024] [<ffffffff81193839>] > > > do_vfs_ioctl+0x99/0x330 > > Apr 19 17:38:41 evo kernel: [ 347.662032] [<ffffffff8118d345>] ? > > > putname+0x35/0x50 > > Apr 19 17:38:41 evo kernel: [ 347.662040] [<ffffffff81193b71>] > > > sys_ioctl+0xa1/0xb0 > > Apr 19 17:38:41 evo kernel: [ 347.662049] [<ffffffff816691a9>] > > > system_call_fastpath+0x16/0x1b > > Fixed by > http://comments.gmane.org/gmane.comp.file-systems.btrfs/16302 > > reported earlier > http://article.gmane.org/gmane.comp.file-systems.btrfs/16796 > > and it's part of 3.4-rc5. >
I was on 3.4-rc5! -- Marco Lorenzo Crociani, marco.croci...@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
