On Mon, 2014-09-22 at 10:45 +0200, Richard Weinberger wrote: > If sync_erase() fails with EINTR, ENOMEM, EAGAIN or > EBUSY erase_worker() re-schedules the failed work. > This will lead to a deadlock because erase_worker() is called > with work_sem held in read mode. And schedule_erase() will take > this lock again. > > Signed-off-by: Richard Weinberger <[email protected]>
Did you manage to test it? Why no -stable this time? Not that important, or just something theoretical and you never actually hit this bug? Thanks! -- Best Regards, Artem Bityutskiy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
