From owner-freebsd-stable@freebsd.org Thu Nov 30 13:56:34 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77162E56FF1 for ; Thu, 30 Nov 2017 13:56:34 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 354CB64CFA for ; Thu, 30 Nov 2017 13:56:34 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 3ynf871y86z1G9 for ; Thu, 30 Nov 2017 14:56:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received:received:received; s=jakla4; t= 1512050167; x=1514642168; bh=KpctVfuIcw48gsTGDAnZVgV0oD94olSPXPQ 6iNN1hzg=; b=Hy+hAQ5OvarH/j1UXhQgbZZofY2KrChjHjXIXEdd+rcufu9iR+I iOUUWLe6tNuuuubnWD3HvfK7tWMHGfvsYYb+UGdb7BaM1VZ/D+D5L+maelSDOBCO bKeT9cE2cIedLR9l7Azk5bZHqu+uX1lo5WCh7AA/GRyDdnj2BcZrT0UI= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id 4K6KZuV7w5lH for ; Thu, 30 Nov 2017 14:56:07 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3ynf7R3X6tz1Fh for ; Thu, 30 Nov 2017 14:55:41 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3ynf7K4S1xzf8 for ; Thu, 30 Nov 2017 14:55:41 +0100 (CET) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by nabiralnik.ijs.si with HTTP (HTTP/1.1 POST); Thu, 30 Nov 2017 14:55:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 30 Nov 2017 14:55:41 +0100 From: Mark Martinec To: freebsd-stable@freebsd.org Subject: Should patch releases to stable 11.1 (errata) include fixes for kernel crashes? Organization: Jozef Stefan Institute Message-ID: <18506e07039fe15655973d3776ea065d@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 13:56:34 -0000 Should patch releases to stable 11.1 (errata) include fixes for kernel crashes? Referring to: Bug 222259 - 11.1-R crashing in sendfile syscall, as used by a uwsgi process https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222259 https://svnweb.freebsd.org/base?view=revision&revision=323634 So my background story is: I fell for this trick twice now, upgrading a 11.1-p3 to -p4, and now a -p4 to -p5 -- forgetting that I need a patched kernel for our web servers (quite a common setup: nginx+uwsgi); so after an upgrade crashes returned. I know, my fault, but I wonder, shouldn't a fix for kernel crashes end up in a patch release of a stable version, with an errata notice? Mark