Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752066AbbHSPpA (ORCPT ); Wed, 19 Aug 2015 11:45:00 -0400 Received: from ipmail06.adl6.internode.on.net ([150.101.137.145]:60681 "EHLO ipmail06.adl6.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750933AbbHSPo6 (ORCPT ); Wed, 19 Aug 2015 11:44:58 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CfAQDUo9RV/3ksAg4NUIRYgyXCIYIQAQEBAQEBhTEnFUABLwYCBRYLAgsDAgECAVUDAQUCAsI4cZYhAQEBAQYCIIEijmNYHoJSgUMFjVOEQYMQjjeOIoIViDCEM2EBgQWBRgEBAQ Message-ID: <55D4A462.3070505@internode.on.net> Date: Thu, 20 Aug 2015 01:14:34 +0930 From: Arthur Marsh User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: linux-mm@kvack.org CC: linux-kernel@vger.kernel.org Subject: difficult to pinpoint exhaustion of swap between 4.2.0-rc6 and 4.2.0-rc7 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2167 Lines: 54 Hi, I've found that the Linus' git head kernel has had some unwelcome behaviour where chromium browser would exhaust all swap space in the course of a few hours. The behaviour appeared before the release of 4.2.0-rc7. This does not happen with kernel 4.2.0-rc6. When I tried a git-bisect, the results where not conclusive due to the problem taking over an hour to appear after booting, the closest I came was around this commit (the actual problem may be a few commits either side): git bisect good 4f258a46346c03fa0bbb6199ffaf4e1f9f599660 is the first bad commit commit 4f258a46346c03fa0bbb6199ffaf4e1f9f599660 Author: Martin K. Petersen Date: Tue Jun 23 12:13:59 2015 -0400 sd: Fix maximum I/O size for BLOCK_PC requests Commit bcdb247c6b6a ("sd: Limit transfer length") clamped the maximum size of an I/O request to the MAXIMUM TRANSFER LENGTH field in the BLOCK LIMITS VPD. This had the unfortunate effect of also limiting the maximum size of non-filesystem requests sent to the device through sg/bsg. Avoid using blk_queue_max_hw_sectors() and set the max_sectors queue limit directly. Also update the comment in blk_limits_max_hw_sectors() to clarify that max_hw_sectors defines the limit for the I/O controller only. Signed-off-by: Martin K. Petersen Reported-by: Brian King Tested-by: Brian King Cc: stable@vger.kernel.org # 3.17+ Signed-off-by: James Bottomley :040000 040000 fbd0519d9ee0a8f92a7dab9a9c6d7b7868974fba b4cf554c568813704993538008aed5b704624679 M block :040000 040000 f2630c903cd36ede2619d173f9d1ea0d725ea111 ff6b6f732afbf6f4b6b26a827c463de50f0e356c M drivers Has anyone seen a similar problem? I can supply .config and other information if requested. Arthur. -- 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/