Project

General

Profile

Actions

Feature #2732

open

103: Check that msleep isn't called with a value in jiffies

Added by Evgeny Novikov almost 12 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Start date:
04/10/2012
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

We should ensure that msleep is called with an argument in milliseconds, not in jiffies (that are returned by msecs_to_jiffies, say).


Related issues 1 (0 open1 closed)

Has duplicate Linux Kernel Safety RuleDB - Feature #3314: 135: msleep and some other functions take time periods in milliseconds, not jiffiesClosedMikhail Mandrykin07/31/2012

Actions
Actions #1

Updated by Evgeny Novikov almost 12 years ago

There is a bug fixed in commit d6b6225 of linux-stable branch, that belongs to specific:check_params:delay class. Model 103_1a finds the bug with help of default BLAST. Commit 2e5a851 of the master branch will contain the model when kent will be repaired.

Actions #2

Updated by Evgeny Novikov almost 12 years ago

I pushed the given commit to QA.

Actions #3

Updated by Alexey Khoroshilov almost 12 years ago

  • Subject changed from Check that msleep isn't called wilth a value in jiffies to 103: Check that msleep isn't called wilth a value in jiffies
Actions #4

Updated by Evgeny Novikov almost 12 years ago

Reduce priority until we'll decide that it's high actually.

Actions #5

Updated by Evgeny Novikov almost 12 years ago

  • Priority changed from High to Normal
Actions #6

Updated by Ilya Shchepetkov over 11 years ago

  • Status changed from Open to Resolved

I have rewritten the model and have added tests (commits e888776 and fab61df of master branch).

Actions #7

Updated by Evgeny Novikov over 10 years ago

  • Subject changed from 103: Check that msleep isn't called wilth a value in jiffies to 103: Check that msleep isn't called with a value in jiffies
Actions

Also available in: Atom PDF