Hi Gahdi, A minor nitpick, kernel SRU templates require a [Fix] section, which details the list of commits that you backported. See https://documentation.ubuntu.com/sru/en/latest/reference/exception- Kernel-Updates/.
Its pretty much the commit list you wrote in your [Impact] section. The [Impact] section is mostly for explaining what the problem is, what causes it and how it presents to users. For the [Test case] section, it would be nice to have a step by step process of the testcase, e.g. compiling that C program, what parameters it needs to work, expected output for being broken, expected output for being fixed. In [Where problems can occur] if a regression were to occur, what would it look like to end users? Can they workaround it? What would the impact to their system be? Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2125142 Title: Hung task when heavily accessing kernfs files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2125142/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
