Those are the two big questions I have as well, and they must be answered before we can consider this patch a real fix.
Unfortunately, I am going to be out of town the rest of the week (customer on-site visit), but if these questions get answered satisfactorily, perhaps we can get the fix out monday.
Btw, I've made a big assumption here that the two loops "go together" and disabled both, but it's possible we only need to disable one or the other. I didn't have time to test that, but it should be tested, in case this is an incorrect assumption. Possibly the error exists only for the first loop.
Those are the two big questions I have as well, and they must be answered before we can consider this patch a real fix.
Unfortunately, I am going to be out of town the rest of the week (customer on-site visit), but if these questions get answered satisfactorily, perhaps we can get the fix out monday.
Btw, I've made a big assumption here that the two loops "go together" and disabled both, but it's possible we only need to disable one or the other. I didn't have time to test that, but it should be tested, in case this is an incorrect assumption. Possibly the error exists only for the first loop.