Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752191AbbKKCZ7 (ORCPT ); Tue, 10 Nov 2015 21:25:59 -0500 Received: from mail-pa0-f43.google.com ([209.85.220.43]:33623 "EHLO mail-pa0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752046AbbKKCZ5 (ORCPT ); Tue, 10 Nov 2015 21:25:57 -0500 Date: Tue, 10 Nov 2015 19:25:52 -0700 From: Jens Axboe To: Linus Torvalds Cc: Al Viro , Sasha Levin , Andrey Ryabinin , Matthew Wilcox , Chuck Ebbert , linux-fsdevel , LKML , Dan Williams Subject: Re: fs: out of bounds on stack in iov_iter_advance Message-ID: <20151111022552.GA30482@kernel.dk> References: <55CB5484.6080000@oracle.com> <20150815161338.4ea210ff@as> <55D1A6D4.3080605@gmail.com> <20150819054650.GD18890@ZenIV.linux.org.uk> <55FB75D0.7060403@oracle.com> <560C5469.5010704@oracle.com> <20151106013402.GT22011@ZenIV.linux.org.uk> <20151106021858.GU22011@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2546 Lines: 74 On Tue, Nov 10 2015, Linus Torvalds wrote: > Al, ping? > > On Thu, Nov 5, 2015 at 7:38 PM, Linus Torvalds > wrote: > > On Thu, Nov 5, 2015 at 6:19 PM, Al Viro wrote: > >> > >> How are we going to handle that one? I can put it into mainline pull > >> request via vfs.git, with Cc: stable, but if e.g. Jens prefers to take it > >> via the block tree, I'll be glad to leave it for him to deal with. > > > > Put it in the vfs tree (I'm hoping for a pull request soon..) > > > > I pulled the block trees from Jens yesterday, so there is presumably > > nothing pending there right now. > > Apparently my "hoping for a pull request soon" was ridiculously optimistic. > > Al, looking at the most recent linux-next, most of the vfs commits > there seem to be committed in the last day or two. I'm getting the > feeling that that is all 4.5 material by now. > > Should I just take the iov patch as-is, since apparently no vfs pull > request is happening this merge cycle? And no, I'm not taking > "developed during the second week of the merge window, and sent in the > last few days of it". I'm done with that. I've got 8 other patches pending for a post core merge, just waiting for the last core pull request to go in. I haven't seen this iov iter fix, though. git://git.kernel.dk/linux-block.git for-linus ---------------------------------------------------------------- Jan Kara (1): brd: Refuse improperly aligned discard requests Jens Axboe (2): MAINTAINERS: add reference to new linux-block list blk-mq: mark __blk_mq_complete_request() static Randy Dunlap (1): block: fix blk-core.c kernel-doc warning Sathyavathi M (1): NVMe: Increase the max transfer size when mdts is 0 Stephan G?nther (2): NVMe: use split lo_hi_{read,write}q NVMe: add support for Apple NVMe controller Vivek Goyal (1): fs/block_dev.c: Remove WARN_ON() when inode writeback fails MAINTAINERS | 1 + block/blk-core.c | 3 +++ block/blk-mq.c | 2 +- block/blk-mq.h | 1 - drivers/block/brd.c | 3 +++ drivers/nvme/host/pci.c | 15 +++++++++------ fs/block_dev.c | 15 ++++++++++++--- 7 files changed, 29 insertions(+), 11 deletions(-) -- Jens Axboe -- 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/