How to handle kernel bug/patch? --- ext4 data corruption

I have a virtual machine running OpenSUSE 12.1 kernel 3.4.11, ext4.
This bug hit me:

Apparent serious progressive ext4 data corruption bug in 3.6.3
https://patchwork.kernel.org/patch/1635091/

It was pretty ugly.

I also have a a vm running OpenSUSE 12.3 kernel 3.7.10, ext4.

  1. How do I verify that OpenSUSE 12.3 kernel 3.7.10 is patched? I tried looking at rpm --changelog but couldn’t determine.

  2. I haven’t patched and compiled a kernel since my Slackware days many years ago. So, is this something OpenSUSE will address (i.e., patched kernel)?

  3. Other options? :\

Thanks.

You might find some clues here https://forums.opensuse.org/english/other-forums/news-announcements/tech-news/479881-stable-linux-kernel-hit-ext4-data-corruption-bug.html
Most probably bug would have been removed in 3.x.x series in openSUSE 12.3

On 04/22/2013 01:56 AM, vazhavandan wrote:
>
> opensuseforumorg42;2549818 Wrote:
>> I have a virtual machine running OpenSUSE 12.1 kernel 3.4.11, ext4.
>> This bug hit me:
>>
>> Apparent serious progressive ext4 data corruption bug in 3.6.3
>> https://patchwork.kernel.org/patch/1635091/
>>
>> It was pretty ugly.
>>
>> I also have a a vm running OpenSUSE 12.3 kernel 3.7.10, ext4.
>>
>> 1) How do I verify that OpenSUSE 12.3 kernel 3.7.10 is patched? I
>> tried looking at rpm --changelog but couldn’t determine.
>>
>> 2) I haven’t patched and compiled a kernel since my Slackware days many
>> years ago. So, is this something OpenSUSE will address (i.e., patched
>> kernel)?
>>
>> 3) Other options? :
>>
>>
>> Thanks.
>
> You might find some clues here http://tinyurl.com/coyt3ll
> Most probably bug would have been removed in 3.x.x series in openSUSE
> 12.3

That bug was short lived, and it was fixed rather quickly by reverting the patch
that caused the problem. The official 12.3 kernel contains the fix.

BTW, most people never saw the bug on their ext4 systems. It mostly affected
systems that were rebooted fairly quickly after start. Once the log buffer had a
chance to wrap, it was OK.