Bug 1991976
| Summary: | block: fix New warning in nvme_setup_discard | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Ming Lei <minlei> |
| Component: | kernel | Assignee: | Ming Lei <minlei> |
| kernel sub component: | Block Layer | QA Contact: | ChanghuiZhong <czhong> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | brdeoliv, czhong, gtiwari, jmoyer |
| Version: | 8.5 | Keywords: | Triaged |
| Target Milestone: | beta | Flags: | minlei:
needinfo?
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-4.18.0-337.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-09 19:27:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ming Lei
2021-08-10 13:53:01 UTC
Hi Changhui, I don't have a reproducer for this BZ, and originally it was reported by Oleksandr Natalenko on Fedora or upstream, and I remember it is very hard to trigger. So I think it is fine to run a sanity test for moving on. Thanks, (In reply to Ming Lei from comment #4) > Hi Changhui, > > I don't have a reproducer for this BZ, and originally it was reported by > Oleksandr Natalenko on Fedora or upstream, and I remember it is very hard to > trigger. > > So I think it is fine to run a sanity test for moving on. > > Thanks, Hi,Ming yes,I tried it and it is not easy to reproduce. I will run sanity test, and feedback the test result as soon as possible. Thanks (In reply to ChanghuiZhong from comment #5) > (In reply to Ming Lei from comment #4) > > Hi Changhui, > > > > I don't have a reproducer for this BZ, and originally it was reported by > > Oleksandr Natalenko on Fedora or upstream, and I remember it is very hard to > > trigger. > > > > So I think it is fine to run a sanity test for moving on. > > > > Thanks, > > Hi,Ming > > yes,I tried it and it is not easy to reproduce. > > I will run sanity test, and feedback the test result as soon as possible. > Hi Changhui, OK, thanks! BTW, Rob mentioned in email, if this bug can't be moved on today, we will have to re-submit it and run the whole BZ procedure again for post-beta. So if possible, can test/update the BZ today? Thanks, Ming (In reply to Ming Lei from comment #6) > > BTW, Rob mentioned in email, if this bug can't be moved on today, we will > have to re-submit > it and run the whole BZ procedure again for post-beta. > > So if possible, can test/update the BZ today? ok, I think I can,I will try to update this bz before the end of today Thanks sanity test passed with 4.18.0-330.el8.mr1132_210811_0355: https://beaker.engineering.redhat.com/jobs/5734978 Setting to verified:tested sanity test passed with kernel-4.18.0-337.el8: https://beaker.engineering.redhat.com/jobs/5740299 All fix patches has included to kernel tree: $ git log kernel-4.18.0-337.el8 --oneline --grep=1991976 218e521b73cd Merge: block: return ELEVATOR_DISCARD_MERGE if possible 6806ca28a0b3 block: return ELEVATOR_DISCARD_MERGE if possible move to verified Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: kernel security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:4356 |