diff options
author | Tejun Heo <tj@kernel.org> | 2013-02-20 15:24:12 -0800 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2013-02-21 17:28:29 +0100 |
commit | e182bb38d7db7494fa5dcd82da17fe0dedf60ecf (patch) | |
tree | 5373b72d6bbd6e9b0bda8fae65dd91f3603c3d54 /fs/cifs/cache.c | |
parent | 1a13c0b181f218bf56a1a6b8edbaf2876b22314b (diff) |
posix-timer: Don't call idr_find() with out-of-range ID
When idr_find() was fed a negative ID, it used to look up the ID
ignoring the sign bit before recent ("idr: remove MAX_IDR_MASK and
move left MAX_IDR_* into idr.c") patch. Now a negative ID triggers
a WARN_ON_ONCE().
__lock_timer() feeds timer_id from userland directly to idr_find()
without sanitizing it which can trigger the above malfunctions. Add a
range check on @timer_id before invoking idr_find() in __lock_timer().
While timer_t is defined as int by all archs at the moment, Andrew
worries that it may be defined as a larger type later on. Make the
test cover larger integers too so that it at least is guaranteed to
not return the wrong timer.
Note that WARN_ON_ONCE() in idr_find() on id < 0 is transitional
precaution while moving away from ignoring MSB. Once it's gone we can
remove the guard as long as timer_t isn't larger than int.
Signed-off-by: Tejun Heo <tj@kernel.org>nnn
Reported-by: Sasha Levin <sasha.levin@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: stable@vger.kernel.org
Link: http://lkml.kernel.org/r/20130220232412.GL3570@htj.dyndns.org
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'fs/cifs/cache.c')
0 files changed, 0 insertions, 0 deletions