Hi Tyler -- > Is this to just quiet a useless compiler warning or is there a place > were we actually use payload_len without initializing it? If we use it > uninitialized, does it cause a crash or do we "handle" it in error > paths? These details are factored in to determine if I need to send this > to the stable team and if distros need to backport it. It also keeps me > from scratching my head a year down the road when someone asks me about > the patch with no commit message. :) This is just to squash a compiler warning. Assuming write_tag_64_packet() works as intended, if it fails to initialize payload_len, it should return an error and the function should skip to the end. I'll re-send the patch with a comment explaining this. -- To unsubscribe from this list: send the line "unsubscribe ecryptfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
