Bug 231639
| Summary: | [Symantec 5.1 bug] kernel thread current->mm dereference in grab_swap_token causes oops | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Andrius Benokraitis <andriusb> |
| Component: | kernel | Assignee: | Jerome Marchand <jmarchan> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Jenner <mjenner> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0 | CC: | dhoward, dzickus, eriley, gcase, linux26port, lwang, neena, ram_pandiri |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHBA-2007-0959 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-11-07 19:43:34 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 154639 | ||
| Bug Blocks: | 217203, 243319 | ||
|
Comment 2
Andrius Benokraitis
2007-03-09 18:02:48 UTC
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP. The patch in is linux-2.6.9-vm-swaptoken-null-mm.patch
>>>>
>>>>
>>>> --- linux-2.6.9/mm/thrash.c~ 2005-04-27 23:35:17.000000000 -0400
>>>> +++ linux-2.6.9/mm/thrash.c 2005-04-27 23:35:49.000000000 -0400
>>>> @@ -50,6 +50,10 @@ void grab_swap_token(void)
>>>> struct mm_struct *mm;
>>>> int reason;
>>>>
>>>> + /* Some kernel threads without mm can fault on behalf of
> others.
>>>> */
>>>> + if (unlikely(!current->mm))
>>>> + return;
>>>> +
>>>> /* We have the token. Let others know we still need it. */
>>>> if (has_swap_token(current->mm)) {
----8<----
neena-
Thanks Neena, I've included RH kernel management to assess this issue. Ram, can you verify the code in Comment #5 has been tested by Symantec? Yes, we have tried this in a patched kernel and it definitely fixes the problem. Regards, Peter Kettle, peter_kettle Patch submitted to rhkernel-list: http://post-office.corp.redhat.com/archives/rhkernel-list/2007-March/msg00716.html This request was evaluated by Red Hat Kernel Team for inclusion in a Red Hat Enterprise Linux maintenance release, and has moved to bugzilla status POST. in 2.6.18-18.el5 2.6.18-18.el5 - Where can I pick this kernel Rita Rita, any word on the testing? I'm assuming Peter's comments above still hold? Also, our QE group is looking into how we can reproduce this, is the setup pretty involved? Confirmed by running testcase in rhts manually... systems stays up running the -43 kernel, panics with ga kernel. We've now completed our own testing and we are happy for you to close this case. Thanks for all of your help. Peter Kettle peter_kettle An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0959.html |