[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170510084602.qchu4psnughxrmsz@lostoracle.net>
Date: Wed, 10 May 2017 01:46:03 -0700
From: Nick Desaulniers <nick.desaulniers@...il.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: akpm@...ux-foundation.org, hannes@...xchg.org,
mgorman@...hsingularity.net, vbabka@...e.cz, minchan@...nel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/vmscan: fix unsequenced modification and access
warning
> You can add
Something that's not clear to me when advised to add, should I be
uploading a v3 with your acked by? I think I got that wrong the last
time I asked (which was my first patch to Linux).
> But I still do not understand which part of the code is undefined and
> why.
It's not immediately clear to me either, but it's super later here...
> is this a bug in -Wunsequenced in Clang
Possibly, I think I already found one earlier tonight.
https://bugs.llvm.org/show_bug.cgi?id=32985
Tomorrow, I'll try to cut down a test case to see if this is indeed a
compiler bug. Would you like me to change the commit message to call
this just a simple clean up, in the meantime?
Thanks,
~Nick
Powered by blists - more mailing lists