On Mon, Jun 14, 2010 at 10:58:49PM +0200, Christoph Hellwig wrote: > On Mon, Jun 14, 2010 at 10:07:23PM +0200, Johannes Hirte wrote: > > I think you're wrong here. I've run into a kernel null pointer dereference > > at > > this point with a NFS exported btrfs filesystem: > > Looks like you've applied the patch to a far too old kernel. It can't > be NULL for quite a while already. >
You're the expert, but it looks like it could be null in 2.6.34 like he says. I'm just looking at vfs_fsync_range() in "git show v2.6.34:fs/sync.c". > If you're testing patches posted to the mailinglists always make sure > you have a recent enough kernel. This actually was merged into the btrfs and the kernel.org trees already. I'm not sure how the btrfs backports work... regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
