From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 35B1CECDFB0 for ; Sat, 14 Jul 2018 21:09:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9B58220850 for ; Sat, 14 Jul 2018 21:09:17 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9B58220850 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ucw.cz Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731356AbeGNV3e (ORCPT ); Sat, 14 Jul 2018 17:29:34 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:44896 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729637AbeGNV3e (ORCPT ); Sat, 14 Jul 2018 17:29:34 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id D9F3B80551; Sat, 14 Jul 2018 23:09:13 +0200 (CEST) Date: Sat, 14 Jul 2018 23:09:13 +0200 From: Pavel Machek To: Guenter Roeck Cc: Willy Tarreau , "ksummit-discuss@lists.linuxfoundation.org" , Greg KH , "linux-kernel@vger.kernel.org" Subject: Re: [Ksummit-discuss] bug-introducing patches Message-ID: <20180714210913.GA31065@amd> References: <20180501200019.GA7397@sasha-vm> <20180501205448.GE10479@thunk.org> <20180501220228.GD7397@sasha-vm> <20180502043017.GA11938@1wt.eu> <20180502194139.GA18390@sasha-vm> <20180502200229.GA12729@1wt.eu> <20180714173812.xhfwtcijlxebmn2k@devuan> <20180714194716.GA27381@amd> <4fbbb00c-dcc1-8a2a-a1c6-8d61d545b7b6@roeck-us.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <4fbbb00c-dcc1-8a2a-a1c6-8d61d545b7b6@roeck-us.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > >Well, 0day, kernelci etc... is nice... until the change is in the > >driver. Most of the kernel are drivers, remember? > > > >I don't know. I'd say that if patch is important enough for -stable, > >there should be someone testing it. For core kernel changes, that can > >be 0day bot, but for drivers... > > >=20 > For my part I am just glad that we were able to pick up a fix in xhci code > just last week, tested or not, from -stable, instead of having to track it > down ourselves. Similar for many other driver patches which _do_ affect us > (like the flurry of ext4 patches this week). Granted, there are lots of > patches which we don't use/need, but even there it is surprising how many > problems are found with existing testing. >=20 > For anyone interested in making sure that obscure (whatever that means) > drivers are tested for stable releases, but does not want to spend time o= n it, > all I can recommend is to implement qemu support for it and let me know, > and I'll be happy to add a respective test to my test farm. Umm. Yes, qemu support for every driver would be nice, but will not happen. > However, ultimately, stable release candidates are public. Everyone is > invited to test them. Anyone interested in a specific release and > driver Yes, they are public. SubmittingPatches says every patch should be tested, and that's clearly not happening for -stable. And I'd like those patch marked such. > >And problem exists on mainline, too. > > > >Hmm. Patch for obscure driver. Wow, nice, is WellKnownName actually > >using that driver? Aha, no, he is not; he is doing global > >search&replace, and did not test the patch... > > >=20 > Ah, like me with the strncpy(x, y, strlen(y)) -> memcpy() replacements > I did a week or so ago ? You are right, I only compile tested those and > otherwise trusted my ability to understand C code. If that caused any > problems, please let me know, and hopefully I'll be able to learn somethi= ng > from it. Yes, such stuff. No, I was not talking about you. I did not want to give concrete example, but... # > get_monotonic_boottime() is deprecated, so let's convert this to # > the simpler ktime_get_boot_ns(). # > # > Signed-off-by: #=20 # Have you tested it? # =2E.. # > - curr_boot =3D timespec_to_ns(&boot_time) * cpus; #=20 # Original code is pretty weird (notice the * cpus), so I'm # double-checking. Yes, often you can guess that patch was probably not tested, but it would be nice to have Tested: compile annotation to take away the guesswork. It took me a while an some head scratching in this concrete example, and it is not first time this happened. Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAltKZnkACgkQMOfwapXb+vIKmgCglFAZdOe8KNIzNewX6hFTj+QP EhcAmgOBb8PVJoxJpMp794mLW8LEgaBx =N9aT -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/--