diff options
author | Bjorn Helgaas <bjorn.helgaas@hp.com> | 2010-10-26 15:41:28 -0600 |
---|---|---|
committer | Jesse Barnes <jbarnes@virtuousgeek.org> | 2010-10-26 15:33:28 -0700 |
commit | a1862e31079149a52b6223776228c3aee493d4a7 (patch) | |
tree | f70f7e3f33f63dcf77428b745f0dd01ecbee8e24 /fs/compat.c | |
parent | 6909ba14c25b4db6be2ff89f4fa0fac2d70151a0 (diff) |
resources: handle overflow when aligning start of available area
If tmp.start is near ~0, ALIGN(tmp.start) may overflow, which would
make us think there's more available space than there really is. We
would likely return something that conflicts with a previous resource,
which would cause a failure when allocate_resource() requests the newly-
allocated region.
Reference: https://bugzilla.redhat.com/show_bug.cgi?id=646027
Reported-by: Fabrice Bellet <fabrice@bellet.info>
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'fs/compat.c')
0 files changed, 0 insertions, 0 deletions