No it wasn't yet in the last run. That OOM happened while I compiled the 
last change.
I ran another test with the trace_printk: See attached. Again I ran only 
a kernel compilation.

Ralf-Peter

On 16.08.2016 00:32, Michal Hocko wrote:
> On Mon 15-08-16 11:42:11, Ralf-Peter Rohbeck wrote:
>> This time the OOM killer hit much quicker. No btrfs balance, just compiling
>> the kernel with the new change did it.
>> Much smaller logs so I'm attaching them.
> Just to clarify. You have added the trace_printk for
> try_to_release_page, right? (after fixing it of course). If yes there is
> no single mention of that path failing which would support Joonsoo's
> theory... Could you try with his patch?


----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.