linux-kernel - Re: [PATCH] ipc:fix the wrong use of schedule_hrtimeout_range

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 28 Oct 2011 09:36:13 +0800
From:	Wanlong Gao <gaowanlong@...fujitsu.com>
To:	Wanlong Gao <gaowanlong@...fujitsu.com>
CC:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Carsten Emde <C.Emde@...dl.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>, jslaby@...e.cz,
	Greg KH <gregkh@...e.de>
Subject: Re: [PATCH] ipc:fix the wrong use of schedule_hrtimeout_range_clock()

Anyone else should be added to cc?


On 09/22/2011 02:35 PM, Wanlong Gao wrote:

> Fix the wrong use of schedule_hrtimeout_range_clock() in wq_sleep(), although
> it is harmless for the syscall mq_timed* now.
> It's introduced by 9ca7d8e.
> 
> Signed-off-by: Wanlong Gao <gaowanlong@...fujitsu.com>
> ---
>  ipc/mqueue.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/ipc/mqueue.c b/ipc/mqueue.c
> index ed049ea..2e0ecfc 100644
> --- a/ipc/mqueue.c
> +++ b/ipc/mqueue.c
> @@ -449,8 +449,8 @@ static int wq_sleep(struct mqueue_inode_info *info, int sr,
>  		set_current_state(TASK_INTERRUPTIBLE);
>  
>  		spin_unlock(&info->lock);
> -		time = schedule_hrtimeout_range_clock(timeout,
> -		    HRTIMER_MODE_ABS, 0, CLOCK_REALTIME);
> +		time = schedule_hrtimeout_range_clock(timeout, 0,
> +			HRTIMER_MODE_ABS, CLOCK_REALTIME);
>  
>  		while (ewp->state == STATE_PENDING)
>  			cpu_relax();


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/