On Wed, Feb 26, 2014 at 12:11 AM, Jiri Kosina <jkos...@suse.cz> wrote: > The problem encountered was described as follows: > It's not memory reclamation that is the problem as such. There is > an indirect dependency between network filesystems writing back > pages and ipoib_cm_tx_init() due to how a kworker is used. Page > reclaim cannot make forward progress until ipoib_cm_tx_init() > succeeds and it is stuck in page reclaim itself waiting for network > transmission. Ordinarily this sitaution may be avoided by having > the caller use GFP_NOFS but ipoib_cm_tx_init() does not have > that information.
So to hit the bug, one just needs to attempt doing NFS client mount over an IP subnet served by IPoIB NIC that uses connected-mode and runs over mlx4 device? Or this happens when the connection is going through teardown/re-establishment or something else? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
