From owner-freebsd-current@freebsd.org Sun Nov 8 02:24:15 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5C7852E3022 for ; Sun, 8 Nov 2020 02:24:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CTHxp4hsCz4cd6 for ; Sun, 8 Nov 2020 02:24:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x72d.google.com with SMTP id t191so3739269qka.4 for ; Sat, 07 Nov 2020 18:24:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=irhTo7eJhRQJNQY3LiJkVff250qCGj+60nnjhi9PNjM=; b=Pt6UnDOdN9ey7J0GpY5AgM+qu+8lawWrdD8UW+ZeTA77WCe2i7j+/8llzCEpRDClBe jj+lMy+n4CpxIxHHLlK5HdFr3gElVHQdhPhVAunn3vJpapA8K2Q+ehJM/NsZzhlCCjv3 wFw2/n2F+N7XTv/DwZvH5xHcxdPxI+RHLq4xhoIqZ68o0CXkbkxBZxXLjtnfdhS54N76 vqXnibUvuVuGVoCm/3PByRj+SNG93HPLcbrU4+uyIyN9dvg5CI/ImgWqSol+UNfsiw7r Olhr5RtybNKOEOyP5O7/8iAcZl5025Tj83jdYYDhfrctxfZJJS4gUKuX3AMzSwZsOM8m 70hw== X-Gm-Message-State: AOAM533li5YgE+ydiVnmhe7mGKLeYgZhHc4m3bSG3Ch0u7kQOZmmiNaQ IY5Wows+wABYLnjSE8QBaTEDTGTAD7hSwjdpB7P4Q0gn3kObzyIT X-Google-Smtp-Source: ABdhPJxeKEFuwxBZhxYtf0KE33uINM4I+iPjuQn4aTE0DMi/D1ibKEGVPASNS+4S9u/yebliduAO9AYpSg5SonMagIM= X-Received: by 2002:a05:620a:15b6:: with SMTP id f22mr8303199qkk.44.1604802253295; Sat, 07 Nov 2020 18:24:13 -0800 (PST) MIME-Version: 1.0 References: <20201107162050.38fac464@ernst.home> <20201108094336.4638ce33f22bf408cda31e52@dec.sakura.ne.jp> In-Reply-To: <20201108094336.4638ce33f22bf408cda31e52@dec.sakura.ne.jp> From: Warner Losh Date: Sat, 7 Nov 2020 19:24:02 -0700 Message-ID: Subject: Re: update UPDATING after malloc code change To: Tomoaki AOKI Cc: FreeBSD Current X-Rspamd-Queue-Id: 4CTHxp4hsCz4cd6 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.54 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; URI_COUNT_ODD(1.00)[1]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::72d:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72d:from]; NEURAL_HAM_SHORT(-0.54)[-0.539]; R_SPF_NA(0.00)[no SPF record]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::72d:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2020 02:24:15 -0000 On Sat, Nov 7, 2020 at 5:43 PM Tomoaki AOKI wrote: > On Sun, 8 Nov 2020 00:22:26 +0100 > Guido Falsi wrote: > > > On 07/11/20 17:20, Gary Jennejohn wrote: > > > It seems like an entry should be added to /usr/src/UPDATING, since the > change made > > > to the malloc code causes panics with KMODs from ports if they haven't > been > > > re-compiled. My nvidia-driver also caused a panic with a new kernel. > > > > > > A reminder/warning would be useful. > > > > > > > Why? Rebuilding kmods every time you update the kernel sources is > > already required by default. > > IIRC, there's no official documentation for it. > There is a warning to disable to old modules, which is close... > Adding new NOTE for it into UPDATING (before the first dated entry) > would be a good idea, as someone encounterd problem would read it > to confirm any cautions. > https://svnweb.freebsd.org/base?view=revision&revision=367474 has my take on that. Please let me know what you think. Warner > > You should be surprised when the old kmods still work, not the other way > > around. > > +1. > > > > > -- > > Guido Falsi > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > -- > Tomoaki AOKI > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >