From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Cyrus-Session-Id: sloti22d1t05-1187825-1520886149-2-9669412741587897861 X-Sieve: CMU Sieve 3.0 X-Spam-known-sender: no X-Spam-score: 0.0 X-Spam-hits: BAYES_00 -1.9, FREEMAIL_FORGED_FROMDOMAIN 0.249, FREEMAIL_FROM 0.001, HEADER_FROM_DIFFERENT_DOMAINS 0.25, RCVD_IN_DNSWL_HI -5, T_RP_MATCHES_RCVD -0.01, LANGUAGES en, BAYES_USED global, SA_VERSION 3.4.0 X-Spam-source: IP='209.132.180.67', Host='vger.kernel.org', Country='CN', FromHeader='com', MailFrom='org' X-Spam-charsets: plain='utf-8' X-Resolved-to: greg@kroah.com X-Delivered-to: greg@kroah.com X-Mail-from: stable-owner@vger.kernel.org ARC-Seal: i=1; a=rsa-sha256; cv=none; d=messagingengine.com; s=arctest; t=1520886149; b=De5Yfpm76ZzBV3ov5wJgNB+IvOk87hecL2oKw+R2Ylg6+In +WAdEIy+/KE/6RT75ZzK2euIKFg42ZY2wdJja1DT8BBK7Dz0WLfJsf7BLDhlDUaG I6+8LbjCl7PRa9Xxf3eeNjIi9D4g+tA943l8gbKhCW9hw1hnFiVNNmBxEnSJF7rt U7Wl99/fVvPNkUBmhxX93XFA6BpyH82AcIMN3MFCU9UyTiXKLi36rhYpI560Tx2u w/Gg81KpoDhFH8riAxBhvWg/MEcsxoxM1zJ7bxTfAK1rQ++1SENlQpBArmqnmEMI a9ZU/FU5z9quw5Trk3F1Nh06y5Cn9r94bzQ4o2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=subject:to:references:cc:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding:sender:list-id; s=arctest; t= 1520886149; bh=eLdl2fUD7V7LGF3JQxibdMnb0XtZGaB1yPSWDRQ4lvk=; b=J 2l+cHS8q1OZWbmtSggL4fpJcyMfBlAyxN1OMLi/xuvkKPhUYusZ6VtUo4zxEcZgI Wh73KLZb/sk3WVHmc87iTs7D7sKfFIPQrU2gZi2dtofcJswpvyyrsVFDpiFR+PsZ XZKNd9jxMlHgRX/PEBQBuvaKOwDNURp+Y1gGoBXTNS7PuKOpRaKxeIo1PAts8Yr2 MJ514U7RFfQL4k9p3mxyR1fEa+jCsN6r3VYXAMqdOcZWMlTE2q41mkzRgtMyiHnx fiMqXhhvqEQg1r+DvOcLJFgNBdsT9QCz0WuhOGsy03tcLm8hTU7ZhCiYfx5hhg9F Tg1Uw/a9oZ1KL9hlAichw== ARC-Authentication-Results: i=1; mx2.messagingengine.com; arc=none (no signatures found); dkim=pass (2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=I0c1Ag0U x-bits=2048 x-keytype=rsa x-algorithm=sha256 x-selector=20161025; dmarc=pass (p=none,has-list-id=yes,d=none) header.from=gmail.com; iprev=pass policy.iprev=209.132.180.67 (vger.kernel.org); spf=none smtp.mailfrom=stable-owner@vger.kernel.org smtp.helo=vger.kernel.org; x-aligned-from=fail; x-category=clean score=-100 state=0; x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net header.i=@1e100.net header.b=tgNwRLrH; x-ptr=pass x-ptr-helo=vger.kernel.org x-ptr-lookup=vger.kernel.org; x-return-mx=pass smtp.domain=vger.kernel.org smtp.result=pass smtp_org.domain=kernel.org smtp_org.result=pass smtp_is_org_domain=no header.domain=gmail.com header.result=pass header_is_org_domain=yes Authentication-Results: mx2.messagingengine.com; arc=none (no signatures found); dkim=pass (2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=I0c1Ag0U x-bits=2048 x-keytype=rsa x-algorithm=sha256 x-selector=20161025; dmarc=pass (p=none,has-list-id=yes,d=none) header.from=gmail.com; iprev=pass policy.iprev=209.132.180.67 (vger.kernel.org); spf=none smtp.mailfrom=stable-owner@vger.kernel.org smtp.helo=vger.kernel.org; x-aligned-from=fail; x-category=clean score=-100 state=0; x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net header.i=@1e100.net header.b=tgNwRLrH; x-ptr=pass x-ptr-helo=vger.kernel.org x-ptr-lookup=vger.kernel.org; x-return-mx=pass smtp.domain=vger.kernel.org smtp.result=pass smtp_org.domain=kernel.org smtp_org.result=pass smtp_is_org_domain=no header.domain=gmail.com header.result=pass header_is_org_domain=yes Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932325AbeCLUWJ (ORCPT ); Mon, 12 Mar 2018 16:22:09 -0400 Received: from mail-wm0-f51.google.com ([74.125.82.51]:40744 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932246AbeCLUWI (ORCPT ); Mon, 12 Mar 2018 16:22:08 -0400 X-Google-Smtp-Source: AG47ELt8ECM1eHV7DcAf399cXR0+cB7Ni2JMpPVXyhbfx3RAvY5GUtS/UkTtzWfuC814JwDBdnWP9A== Subject: Re: [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when setting delay_off=0 To: Matthias Schiffer , Greg KH References: <20180203180015.29073-1-alexander.levin@microsoft.com> <20180203180015.29073-65-alexander.levin@microsoft.com> <20180203203525.GA5860@amd> <20180204003029.2lkcmh6wvzpnlrls@sasha-lappy> <20180204090531.GA29468@amd> <20180204111500.GB14797@kroah.com> <20180204171736.GA1388@amd> <20180206020210.m6gl7vai4p6azb6s@sasha-lappy> <713113d8-7662-d80c-c62f-af020469d0bf@gmail.com> <20180312152811.GB16944@kroah.com> <5747831a-b237-aa2c-cb47-9773cd2b5956@universe-factory.net> Cc: Sasha Levin , Pavel Machek , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , Matthieu CASTET , "linux-leds@vger.kernel.org" From: Jacek Anaszewski X-Enigmail-Draft-Status: N1010 Message-ID: <0cd72fe4-2b98-e6f7-6ae7-530524786cec@gmail.com> Date: Mon, 12 Mar 2018 21:20:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <5747831a-b237-aa2c-cb47-9773cd2b5956@universe-factory.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org X-Mailing-List: stable@vger.kernel.org X-getmail-retrieved-from-mailbox: INBOX X-Mailing-List: linux-kernel@vger.kernel.org List-ID: On 03/12/2018 04:45 PM, Matthias Schiffer wrote: > On 03/12/2018 04:28 PM, Greg KH wrote: >> On Mon, Mar 12, 2018 at 04:00:01PM +0100, Matthias Schiffer wrote: >>> On 02/06/2018 09:44 PM, Jacek Anaszewski wrote: >>>> On 02/06/2018 03:02 AM, Sasha Levin wrote: >>>>> On Sun, Feb 04, 2018 at 06:17:36PM +0100, Pavel Machek wrote: >>>>>> >>>>>>>>>>> *** if brightness=0, led off >>>>>>>>>>> *** else apply brightness if next timer <--- timer is stop, and will never apply new setting >>>>>>>>>>> ** otherwise set led_set_brightness_nosleep >>>>>>>>>>> >>>>>>>>>>> To fix that, when we delete the timer, we should clear LED_BLINK_SW. >>>>>>>>>> >>>>>>>>>> Can you run the tests on the affected stable kernels? I have feeling >>>>>>>>>> that the problem described might not be present there. >>>>>>>>> >>>>>>>>> Hm, I don't seem to have HW to test that out. Maybe someone else does? >>>>>>>> >>>>>>>> Why are you submitting patches you have no way to test? >>>>>>> >>>>>>> What? This is stable tree backporting, why are you trying to make a >>>>>>> requirement for something that we have never had before? >>>>>> >>>>>> I don't think random patches should be sent to stable just because >>>>>> they appeared in mainline. Plus, I don't think I'm making new rules: >>>>>> >>>>>> submit-checklist.rst: >>>>>> >>>>>> 13) Has been build- and runtime tested with and without ``CONFIG_SMP`` >>>>>> and >>>>>> ``CONFIG_PREEMPT.`` >>>>>> >>>>>> stable-kernel-rules.rst: >>>>>> >>>>>> Rules on what kind of patches are accepted, and which ones are not, >>>>>> into the "-stable" tree: >>>>>> >>>>>> - It must be obviously correct and tested. >>>>>> - It must fix a real bug that bothers people (not a, "This could be a >>>>>> problem..." type thing). >>>>> >>>>> So you're saying that this doesn't qualify as a bug? >>>>> >>>>>>> This is a backport of a patch that is already upstream. If it doesn't >>>>>>> belong in a stable tree, great, let us know that, saying why it is so. >>>>>> >>>>>> See jacek.anaszewski@gmail.com 's explanation. >>>>> >>>>> I might be missing something, but Jacek suggested I pull another patch >>>>> before this one? >>>> >>>> Just to clarify: >>>> >>>> For 4.14 below patches are chosen correctly: >>>> >>>> [PATCH AUTOSEL for 4.14 065/110] led: core: Fix brightness setting when >>>> setting delay_off=0 >>>> [PATCH AUTOSEL for 4.14 094/110] leds: core: Fix regression caused by >>>> commit 2b83ff96f51d >>>> >>>> For 4.9 both above patches are needed preceded by: >>>> >>>> eb1610b4c273 ("led: core: Fix blink_brightness setting race") >>>> >>>> The issue the patch [PATCH AUTOSEL for 4.14 065/110] fixes was >>>> introduced in 4.7, and thus it should be removed from the series >>>> for 3.18 and 4.4. >>>> >>> >>> It seems only "led: core: Fix brightness setting when setting delay_off=0" >>> was applied to 4.9. Could we get the regression fixes backported to 4.9 as >>> well? >> >> What exact fixes were they? I'll be glad to apply them if I have a git >> commit id. >> >> thanks, >> >> greg k-h >> > > At least 7b6af2c531 ("leds: core: Fix regression caused by commit > 2b83ff96f51d") is missing, causing visible regressions (LEDs not working at > all) on some OpenWrt devices. This was fixed in 4.4.121 by reverting the > offending commit, but if I followed the discussion correctly, 4.9 should > get the follow-up commit 7b6af2c531 instead (like 4.14 already did). > > Jacek's mail I replied to mentions that eb1610b4c273 ("led: core: Fix > blink_brightness setting race") should be included in 4.9 as well, but I > don't know the impact of the issue it fixes. It doesn't fix any reported issue, but is just an improvement aiming at preventing potential races while changing blink brightness. After taking closer look it turns out that for the patches in question to apply cleanly we need in 4.9 also a patch which introduces atomic bit fields for blink flags. Effectively, here is the list of patches required in 4.9 stable: Revert "led: core: Fix brightness setting when setting delay_off=0" followed by: a9c6ce57ec ("led: core: Use atomic bit-field for the blink-flags") eb1610b4c2 ("led: core: Fix blink_brightness setting race") 2b83ff96f5 ("led: core: Fix brightness setting when setting delay_off=0") 7b6af2c531 ("leds: core: Fix regression caused by commit 2b83ff96f51d") -- Best regards, Jacek Anaszewski