Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Eiichi Tsukata <devel@etsukata.com>
To:     mhiramat@kernel.org
Cc:     juri.lelli@gmail.com, linux-kernel@vger.kernel.org,
        mingo@kernel.org, peterz@infradead.org, rostedt@goodmis.org,
        tglx@linutronix.de, torvalds@linux-foundation.org,
        williams@redhat.com, Eiichi Tsukata <devel@etsukata.com>
Subject: [PATCH 0/1] x86/stacktrace: Fix userstacktrace access_ok() WARNING in irq events
Date:   Mon, 22 Jul 2019 17:32:15 +0900
Message-Id: <20190722083216.16192-1-devel@etsukata.com>
In-Reply-To: <20190621231232.259536faeea4b19cf39a7688@kernel.org>
References: <20190621231232.259536faeea4b19cf39a7688@kernel.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hello

I also hit the same WARNING previously repored by Juri.

Hiramatsu san's patch looks good to me but I found that perf and
oprofile code do the similar thing by just directly calling
__range_not_ok().

  perf: perf_callchain_user()@arch/x86/events/core.c
  oprofile: dump_user_backtrace()@arch/x86/oprofile/backtrace.c

So for simplicity, I wrote a patch to fix the warning as other
codes do.

Ideally, we should merge these similar stacktrace codes(perf, ftrace,
oprofile) into one, but this time I made the minimum fix.

Eiichi Tsukata (1):
  x86/stacktrace: Fix userstacktrace access_ok() WARNING in irq events

 arch/x86/kernel/stacktrace.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.21.0