Hi Peter, On Wed, Jun 10, 2015 at 10:11 AM, Peter Hurley <peter@xxxxxxxxxxxxxxxxxx> wrote: > Well, I still couldn't repro this bug but I have a hypothesis that > the bash sig handler is executing before the flush occurs, perhaps > because the flush is stalled waiting for the write lock. > > Would you please try the patch below? Will do! I just reproduced it now on my VM but sometimes it takes longer, so I'll take it for a spin for a few days and report back if I don't see the problem anymore after a week. > PPS - FWIW, the line kill key binding is usually ^U. You can check what > the terminal key bindings are with "stty -a" Not sure why you mention that... I did try ^U and ^W (unix-word-rubout) or even backspace after getting into that weird situation but bash only backs up to where the previous line (the interrupted one) ended. So it doesn't really clear my line. Though anytime I type a valid command there, even though it *looks* wrong, it does execute it correctly, so internally bash seems to have the right idea... Anyways, I'll report back on the patch in a few days. Cheers, Filipe -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
