Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753342AbdIYDuI (ORCPT ); Sun, 24 Sep 2017 23:50:08 -0400 Received: from smtp2.linuxfoundation.org ([140.211.169.14]:36874 "EHLO smtp2.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753000AbdIYDuH (ORCPT ); Sun, 24 Sep 2017 23:50:07 -0400 X-Greylist: delayed 513 seconds by postgrey-1.27 at vger.kernel.org; Sun, 24 Sep 2017 23:50:06 EDT Subject: [Kernel.org Helpdesk #46182] [linuxfoundation.org #46182] Re: Linux 4.14-rc2 (bad patch file on kernel.org) From: "Linus Torvalds via RT" Reply-To: kernel-helpdesk@rt.linuxfoundation.org In-Reply-To: References: Message-ID: X-RT-Loop-Prevention: linuxfoundation.org X-RT-Ticket: linuxfoundation.org #46182 X-Managed-BY: RT 4.4.0 (http://www.bestpractical.com/rt/) X-RT-Originator: torvalds@linux-foundation.org To: rdunlap@infradead.org CC: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Sun, 24 Sep 2017 23:41:33 -0400 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1318 Lines: 34 On Sun, Sep 24, 2017 at 7:57 PM, Randy Dunlap wrote: > > Downloading & applying 4.14-rc2 [patch] > > from kernel.org (home page) gives me a file that does not apply cleanly to v4.13: Hmm. The rc patches are automatically generated from the git tree these days, so I don't have control over them. It does sound like you might have caught it while it was being generated: > patch unexpectedly ends in middle of line > patch: **** unexpected end of file in patch which would seem to indicate that maybe you just caught it while it was still being generated. But I just tried it myself, and get the same breakage. In fact, the patch it downloads is exactly 50397184 bytes in size. That may not sound like a round number, but it is: it is hex 0x3010000, so it's evenly divisible by 65536. Methinks there's some incorrect flushing of block IO going on. Konstantin? > I also notice that the [pgp] signing is not there. Is that normal? So I don't sign the rc patches any more because I don't generate them (but the final release patches and tar-balls I *do* sign). But maybe they could be signed by some kernel.org key. Again, that would be an automation issue.. Linus