On Wed, Feb 14, 2018 at 4:21 PM, Sowmini Varadhan <sowmini.varadhan@xxxxxxxxxx> wrote: > On (02/14/18 16:11), Dmitry Vyukov wrote: >> >> Hi Sowmini, >> >> Was this ever fixed? What's the fix? This still hangs as open. Please >> provide "syz fix" tag. > > Are you still seeing this problem? > > I had expected that the changes around rds_destroy_pending - see commit > ebeeb1ad9b8a - would have taken care of this (note that ebeeb1ad9b8a > refactors/updates 3db6e0d172c9) but those fixes were done by inspection > only. In other words, I was never able to reproduce this, so we may > still have missed some race condition. syzbot is probably not seeing this problem. However if you don't add the Reported-by tag to commit, nor provide syz fix tag, it will consider it as "open". One consequence of this is that it is still on our radars. Another consequence is that syzbot will never report bugs in rds_tcp_tune ever again as it thinks that it's the same known bug, so no point in bothering anybody. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
