From: Christoph Hellwig <hch@lst.de> To: Michal Hocko <mhocko@kernel.org> Cc: Andrew Morton <akpm@linux-foundation.org>, Christoph Hellwig <hch@lst.de>, Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>, Al Viro <viro@zeniv.linux.org.uk>, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>, Michal Hocko <mhocko@suse.com> Subject: Re: [PATCH 1/3] fs: break out of iomap_file_buffered_write on fatal signals Date: Wed, 1 Feb 2017 10:28:26 +0100 [thread overview] Message-ID: <20170201092826.GB1050@lst.de> (raw) In-Reply-To: <20170201092706.9966-2-mhocko@kernel.org> Looks fine, Reviewed-by: Christoph Hellwig <hch@lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: Michal Hocko <mhocko@kernel.org> Cc: Andrew Morton <akpm@linux-foundation.org>, Christoph Hellwig <hch@lst.de>, Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>, Al Viro <viro@zeniv.linux.org.uk>, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>, Michal Hocko <mhocko@suse.com> Subject: Re: [PATCH 1/3] fs: break out of iomap_file_buffered_write on fatal signals Date: Wed, 1 Feb 2017 10:28:26 +0100 [thread overview] Message-ID: <20170201092826.GB1050@lst.de> (raw) In-Reply-To: <20170201092706.9966-2-mhocko@kernel.org> Looks fine, Reviewed-by: Christoph Hellwig <hch@lst.de> -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-02-01 9:28 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-01 9:27 [PATCH 0/3] fix few OOM victim allocation runaways Michal Hocko 2017-02-01 9:27 ` Michal Hocko 2017-02-01 9:27 ` Michal Hocko 2017-02-01 9:27 ` [PATCH 1/3] fs: break out of iomap_file_buffered_write on fatal signals Michal Hocko 2017-02-01 9:27 ` Michal Hocko 2017-02-01 9:27 ` Michal Hocko 2017-02-01 9:28 ` Christoph Hellwig [this message] 2017-02-01 9:28 ` Christoph Hellwig 2017-02-01 9:27 ` [PATCH 2/3] mm, fs: check for fatal signals in do_generic_file_read Michal Hocko 2017-02-01 9:27 ` Michal Hocko 2017-02-01 9:27 ` Michal Hocko 2017-02-01 9:28 ` Christoph Hellwig 2017-02-01 9:28 ` Christoph Hellwig 2017-02-01 9:27 ` [PATCH 3/3] vmalloc: back of when the current is killed Michal Hocko 2017-02-01 9:27 ` Michal Hocko 2017-02-01 9:27 ` Michal Hocko 2017-02-01 9:28 ` Christoph Hellwig 2017-02-01 9:28 ` Christoph Hellwig 2017-02-01 11:49 ` [PATCH 0/3] fix few OOM victim allocation runaways Tetsuo Handa 2017-02-01 11:49 ` Tetsuo Handa
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20170201092826.GB1050@lst.de \ --to=hch@lst.de \ --cc=akpm@linux-foundation.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@kernel.org \ --cc=mhocko@suse.com \ --cc=penguin-kernel@I-love.SAKURA.ne.jp \ --cc=viro@zeniv.linux.org.uk \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.