Skip to contentSkip to conversation

Bug 586009 - CVE-2010-1436 kernel: oops while cp from ext3 to gfs2 [rhel-6.0]

PATCH New Abhijith Das 2 participants 2 messages May 7, 2010 – May 10, 2010 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 924012423.251581273268920873.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com

#1 lore raw

PATCH 1/1 Bug 586009 - CVE-2010-1436 kernel: oops while cp from ext3 to gfs2 [rhel-6.0]

This is the upstream/rhel6 fix for this bug. This patch differs from the RHEL5 fix (555754) which simply writes to the 8-byte value field of the quota. In upstream/rhel6 quota code, we're required to write the entire quota (88 bytes) which can be split across a page boundary. We check for such quotas, and read/write the two parts from/to the corresponding pages holding these parts.

With this patch, I don't see the bug anymore using the reproducer in bz 555754. I successfully ran a couple of simple tests/mounts/ umounts and it doesn't seem like this patch breaks anything else.

Resolves: rhbz#586009

-------------- next part --------------
A non-text attachment was scrubbed...
Name: bz586009-try3.patch
Type: text/x-patch
Size: 4113 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20100507/f7fbedf6/attachment.bin>

#2 lore raw

PATCH 1/1 Bug 586009 - CVE-2010-1436 kernel: oops while cp from ext3 to gfs2 [rhel-6.0]

Hi,

Now in the -nmw git tree. Thanks,

Steve

Quoted 13 lines · Abhijith Das

This is the upstream/rhel6 fix for this bug. This patch differs from the RHEL5 fix (555754) which simply writes to the 8-byte value field of the quota. In upstream/rhel6 quota code, we're required to write the entire quota (88 bytes) which can be split across a page boundary. We check for such quotas, and read/write the two parts from/to the corresponding pages holding these parts.

With this patch, I don't see the bug anymore using the reproducer in bz 555754. I successfully ran a couple of simple tests/mounts/ umounts and it doesn't seem like this patch breaks anything else.

Resolves: rhbz#586009