Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932835AbdIYDl2 (ORCPT ); Sun, 24 Sep 2017 23:41:28 -0400 Received: from mail-io0-f175.google.com ([209.85.223.175]:46841 "EHLO mail-io0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932076AbdIYDl1 (ORCPT ); Sun, 24 Sep 2017 23:41:27 -0400 X-Google-Smtp-Source: AOwi7QCZ1rHBywWVlu1Azd50lCuS7qw9A2NoNUPQy/A4hbpu4H+R9VFsPyAChyyQihB7zjXdjPSlApNJZF6BRtdg6nU= MIME-Version: 1.0 In-Reply-To: References: From: Linus Torvalds Date: Sun, 24 Sep 2017 20:41:25 -0700 X-Google-Sender-Auth: GSxNHjbsINf8H2H6snGrLu98Fzw Message-ID: Subject: Re: Linux 4.14-rc2 (bad patch file on kernel.org) To: Randy Dunlap , Konstantin Ryabitsev Cc: Linux Kernel Mailing List , helpdesk@kernel.org Content-Type: text/plain; charset="UTF-8" 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