On Tue, Jul 02, 2013 at 08:04:47PM +0200, Jan Kara wrote: > That's caused by my patches (only for certain gcc versions). map->m_len > is guaranteed to be > 0 in the first iteration (the function is called from > under if (map->m_len > 0)). I though Ted silenced that warning but > apparently he did not. The cleanest fix is likely to make a do-while loop > from that one. I'll send Ted a patch for that. Sorry, I fixed it with a code simplification (I thought the while loop wasn't needed at all), but when you explained why in fact we still needed it, I dropped my commit, and forgot that this also dropped the fix which silenced the warning. I'll grab your patch and included with any other fixes that we might need for this merge window. Linus, are you in a hurry to get this fixed up? It's a false warning on gcc's part, so it's not actually causing any actual problems. If not, I can wait until a week or so to see if there are any other bug fixes that are required and push the fix to you towards the end of the merge window. - Ted -- 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
