From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932486AbVHYV1F (ORCPT ); Thu, 25 Aug 2005 17:27:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932570AbVHYV1E (ORCPT ); Thu, 25 Aug 2005 17:27:04 -0400 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]:54658 "EHLO zcars04f.nortelnetworks.com") by vger.kernel.org with ESMTP id S932486AbVHYV1E (ORCPT ); Thu, 25 Aug 2005 17:27:04 -0400 Message-ID: <430E37A0.1000304@nortel.com> Date: Thu, 25 Aug 2005 15:26:56 -0600 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: "Christopher Friesen" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vadim Lobanov CC: linux-kernel@vger.kernel.org, tom.anderl@gmail.com Subject: Re: [OT] volatile keyword References: <430E30B2.1020700@nortel.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Vadim Lobanov wrote: > I figured it was something along these lines. In that case, is the > following code (from kernel/posix-timers.c) really doing the right > thing? > > do > expires = timr->it_timer.expires; > while ((volatile long) (timr->it_timer.expires) != expires); > > Seems it's casting the value, not the pointer. Someone else will have to give the definitive answer, but it looks suspicious to me... Chris