Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965581AbaGPRIs (ORCPT ); Wed, 16 Jul 2014 13:08:48 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:48571 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752706AbaGPRIp (ORCPT ); Wed, 16 Jul 2014 13:08:45 -0400 Message-ID: <53C6B199.2070606@gmail.com> Date: Wed, 16 Jul 2014 20:08:41 +0300 From: Boaz Harrosh User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Christoph Hellwig , pramod.gurav.etc@gmail.com, viro@zeniv.linux.org.uk, Jason Cooper , Markus Mayer , Paul Bolle CC: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] fs/direct-io.c: Fix compilation warning for uninitialized variables References: <1404452632-10912-1-git-send-email-pramod.gurav.etc@gmail.com> <20140713115022.GA6054@infradead.org> In-Reply-To: <20140713115022.GA6054@infradead.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/13/2014 02:50 PM, Christoph Hellwig wrote: > pramod.gurav.etc@gmail.com wrote ... >> diff --git a/fs/direct-io.c b/fs/direct-io.c >> index 98040ba388ac..c0a9854d2bc7 100644 >> --- a/fs/direct-io.c >> +++ b/fs/direct-io.c >> @@ -910,7 +910,8 @@ static int do_direct_IO(struct dio *dio, struct dio_submit *sdio, >> >> while (sdio->block_in_file < sdio->final_block_in_request) { >> struct page *page; >> - size_t from, to; >> + size_t from = 0; >> + size_t to = 0; >> page = dio_get_page(dio, sdio, &from, &to); >> if (IS_ERR(page)) { >> ret = PTR_ERR(page); > Looks good to me, > > Reviewed-by: Christoph Hellwig > > Al, can you pick this up? It's the only warnings in many of my usual > kernel builds at the moment. > <> Paul Bolle wrote ... <> > @@ -911,11 +907,15 @@ static int do_direct_IO(struct dio *dio, struct dio_submit *sdio, > while (sdio->block_in_file < sdio->final_block_in_request) { > struct page *page; > size_t from, to; > - page = dio_get_page(dio, sdio, &from, &to); > + > + page = dio_get_page(dio, sdio); > if (IS_ERR(page)) { > ret = PTR_ERR(page); > goto out; > } > + from = sdio->head ? 0 : sdio->from; > + to = (sdio->head == sdio->tail - 1) ? sdio->to : PAGE_SIZE; > + sdio->head++; > > while (from < to) { > unsigned this_chunk_bytes; /* # of bytes mapped */ <> This is the wrong fix. GCC is wrong here. As shown by Paul Bolle if you move the from / to set from dio_get_page() to here the warning goes away. The minimal fix must use uninitialized_var() in this case. See patch below But I think the proper fix Is the one Paul Bolle sent (above) ---- From: Boaz Harrosh Date: Wed, 16 Jul 2014 20:02:29 +0300 Subject: [PATCH] do_direct_IO: Fix compiler warning MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This fixes ../fs/direct-io.c: In function ‘do_blockdev_direct_IO’: ../fs/direct-io.c:1011:12: warning: ‘from’ may be used uninitialized in this function [-Wmaybe-uninitialized] u = (to - from) >> blkbits; ^ ../fs/direct-io.c:1011:12: warning: ‘to’ may be used uninitialized in this function [-Wmaybe-uninitialized] u = (to - from) >> blkbits; I use: gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) GCC is wrong here so we should use the uninitialized_var() macro and not silence it with = 0; Signed-off-by: Boaz Harrosh --- fs/direct-io.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/direct-io.c b/fs/direct-io.c index 98040ba..156e6f0 100644 --- a/fs/direct-io.c +++ b/fs/direct-io.c @@ -910,7 +910,8 @@ static int do_direct_IO(struct dio *dio, struct dio_submit *sdio, while (sdio->block_in_file < sdio->final_block_in_request) { struct page *page; - size_t from, to; + size_t uninitialized_var(from), uninitialized_var(to); + page = dio_get_page(dio, sdio, &from, &to); if (IS_ERR(page)) { ret = PTR_ERR(page); -- 1.9.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/