On Thu, Feb 17, 2022 at 10:51:09AM -0500, Theodore Ts'o wrote: > On Thu, Feb 17, 2022 at 07:57:36PM +0900, Byungchul Park wrote: > > > > I've got several reports from the tool. Some of them look like false > > alarms and some others look like real deadlock possibility. Because of > > my unfamiliarity of the domain, it's hard to confirm if it's a real one. > > Let me add the reports on this email thread. > > The problem is we have so many potentially invalid, or > so-rare-as-to-be-not-worth-the-time-to-investigate-in-the- > grand-scheme-of-all-of-the-fires-burning-on-maintainers laps that it's > really not reasonable to ask maintainers to determine whether Even though I might have been wrong and might be gonna be wrong, you look so arrogant. You were hasty to judge and trying to walk over me. I reported it because I thought it was a real problem but couldn't confirm it. For the other reports that I thought was not real, I didn't even mention it. If you are talking about the previous report, then I felt so sorry as I told you. I skimmed through the part of the waits... Basically, I respect you and appreciate your feedback. Hope you not get me wrong. > Looking at the second ext4 report, it doesn't make any sense. Context > A is the kjournald thread. We don't do a commit until (a) the timeout > expires, or (b) someone explicitly requests that a commit happen > waking up j_wait_commit. I'm guessing that complaint here is that > DEPT thinks nothing is explicitly requesting a wake up. But note that > after 5 seconds (or whatever journal->j_commit_interval) is configured > to be we *will* always start a commit. So ergo, there can't be a deadlock. Yeah, it might not be a *deadlock deadlock* because the wait will be anyway woken up by one of the wake up points you mentioned. However, the dependency looks problematic because the three contexts participating in the dependency chain would be stuck for a while until one eventually wakes it up. I bet it would not be what you meant. Again. It's not critical but problematic. Or am I missing something? > At a higher level of discussion, it's an unfair tax on maintainer's > times to ask maintainers to help you debug DEPT for you. Tools like > Syzkaller and DEPT are useful insofar as they save us time in making > our subsystems better. But until you can prove that it's not going to > be a massive denial of service attack on maintainer's time, at the Partially I agree. I would understand you even if you don't support Dept until you think it's valuable enough. However, let me keep asking things to fs folks, not you, even though I would cc you on it. > If you know there there "appear to be false positives", you need to > make sure you've tracked them all down before trying to ask that this > be merged. To track them all down, I need to ask LKML because Dept works perfectly with my system. I don't want it to be merged with a lot of false positive still in there, either. > You may also want to add some documentation about why we should trust > this; in particular for wait channels, when a process calls schedule() > there may be multiple reasons why the thread will wake up --- in the > worst case, such as in the select(2) or epoll(2) system call, there > may be literally thousands of reasons (one for every file desriptor > the select is waiting on) --- why the process will wake up and thus > resolve the potential "deadlock" that DEPT is worrying about. How is > DEPT going to handle those cases? If the answer is that things need Thank you for the information but I don't get it which case you are concerning. I'd like to ask you a specific senario of that so that we can discuss it more - maybe I guess I could answer to it tho, but I won't ask you. Just give me an instance only if you think it's worthy. You look like a guy who unconditionally blames on new things before understanding it rather than asking and discussing. Again. I also think anyone doesn't have to spend his or her time for what he or she think is not worthy enough. > I know that you're trying to help us, but this tool needs to be far > better than Lockdep before we should think about merging it. Even if > it finds 5% more potential deadlocks, if it creates 95% more false It should not get merged for sure if so, but it sounds too sarcastic. Let's see if it creates 95% false positives for real. If it's true and I can't control it, I will give up. That's what I should do. There are a lot of factors to judge how valuable Dept is. Dept would be useful especially in the middle of development, rather than in the final state in the tree. It'd be appreciated if you think that sides more, too. Thanks, Byungchul
