I've added your patch to the patch queue, using the following commit comment, and using it to replace aneesh-9-fix-lockdeep-recursive-locking-warning in the patch queue. Please note that commit description explains what was the problem you were trying to solve, some notes about why this works, what the limitations might be with the approach. This is the kind of commit logs we should strive for. We've been complemented for the clarity of our commit logs, and much of that is because I've been rewriting the changelog messages. If everyone who submits patches could strive to meet similar standards, I'd greatly appreciated. - Ted ext4: Fix lockdep recursive locking warning From: "Aneesh Kumar K.V" <aneesh.kumar@xxxxxxxxxxxxxxxxxx> In ext4_mb_init_group(), if the filesystem block size is less than PAGE_SIZE/2, the code tries to grab alloc_sem for multiple block groups in a loop. We need to allow for this by using down_write_nested() and passing in the loop index as a lock subclass number. This works because no other code path needs to take multiple alloc_sem's. Note that lockdep will fail for filesystem blocksize smaller than to PAGE_SIZE/16k. (e.g., a 1k filesystem blocksize with a 32k page size, or a 2k filesystem blocksize with a 64k blocksize, etc.) -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
