| Bug ID | 960628 |
|---|---|
| Summary | raid10 kernel module crashes with BUG during re-syncing process in kernel 4.3.3-3.1.x86_64 |
| Classification | openSUSE |
| Product | openSUSE Tumbleweed |
| Version | 2015* |
| Hardware | x86-64 |
| OS | SUSE Other |
| Status | NEW |
| Severity | Critical |
| Priority | P5 - None |
| Component | Kernel |
| Assignee | kernel-maintainers@forge.provo.novell.com |
| Reporter | jared.hudson@microfocus.com |
| QA Contact | qa-bugs@suse.de |
| Found By | --- |
| Blocker | --- |
After I create a new RAID 10 device using mdadm or yast2 disk the kernel ring buffer shows a BUG and stack trace due to bad pointer dereference in bio_copy_data(). Making the change shown in this commit fixed the problem. md/raid10: fix data corruption and crash during resync https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cc57858831e3e9678291de730c4b4d2e52a19f59 You may also want to apply this patch as well but I've not tested it yet. md: remove check for MD_RECOVERY_NEEDED in action_store https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=312045eef985b61d74c28047ecd8eca6719d9516 I'm at work and don't have access to a Tumbleweed installation otherwise I'd post the whole stack trace. I will post these details in the next few hours.