* Re: Please apply d2155fe54ddb to 5.10 and 5.4 [not found] ` <2025042251-energize-preorder-31cd@gregkh> @ 2025-04-22 6:10 ` Qingfang Deng 2025-04-22 6:27 ` Greg Kroah-Hartman 0 siblings, 1 reply; 8+ messages in thread From: Qingfang Deng @ 2025-04-22 6:10 UTC (permalink / raw) To: Greg Kroah-Hartman Cc: Sasha Levin, stable, linux-mm, Zi Yan, Johannes Weiner, Brendan Jackman, Michal Hocko, Suren Baghdasaryan, Vlastimil Babka, Andrew Morton, Liu Xiang, David Hildenbrand On Tue, Apr 22, 2025 at 2:06 PM Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > All mm patches MUST get approval from the mm maintainers/developers > before we can apply them to stable kernels. > > Can you please do that here? Sure. Added to Cc list. > > thanks, > > greg k-h ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Please apply d2155fe54ddb to 5.10 and 5.4 2025-04-22 6:10 ` Please apply d2155fe54ddb to 5.10 and 5.4 Qingfang Deng @ 2025-04-22 6:27 ` Greg Kroah-Hartman 2025-04-22 6:34 ` Qingfang Deng 0 siblings, 1 reply; 8+ messages in thread From: Greg Kroah-Hartman @ 2025-04-22 6:27 UTC (permalink / raw) To: Qingfang Deng Cc: Sasha Levin, stable, linux-mm, Zi Yan, Johannes Weiner, Brendan Jackman, Michal Hocko, Suren Baghdasaryan, Vlastimil Babka, Andrew Morton, Liu Xiang, David Hildenbrand On Tue, Apr 22, 2025 at 02:10:53PM +0800, Qingfang Deng wrote: > On Tue, Apr 22, 2025 at 2:06 PM Greg Kroah-Hartman > <gregkh@linuxfoundation.org> wrote: > > All mm patches MUST get approval from the mm maintainers/developers > > before we can apply them to stable kernels. > > > > Can you please do that here? > > Sure. Added to Cc list. They have no context here at all :( ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Please apply d2155fe54ddb to 5.10 and 5.4 2025-04-22 6:27 ` Greg Kroah-Hartman @ 2025-04-22 6:34 ` Qingfang Deng 2025-04-22 7:04 ` David Hildenbrand 0 siblings, 1 reply; 8+ messages in thread From: Qingfang Deng @ 2025-04-22 6:34 UTC (permalink / raw) To: Greg Kroah-Hartman Cc: Sasha Levin, stable, linux-mm, Zi Yan, Johannes Weiner, Brendan Jackman, Michal Hocko, Suren Baghdasaryan, Vlastimil Babka, Andrew Morton, Liu Xiang, David Hildenbrand On Tue, Apr 22, 2025 at 2:27 PM Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > On Tue, Apr 22, 2025 at 02:10:53PM +0800, Qingfang Deng wrote: > > On Tue, Apr 22, 2025 at 2:06 PM Greg Kroah-Hartman > > <gregkh@linuxfoundation.org> wrote: > > > All mm patches MUST get approval from the mm maintainers/developers > > > before we can apply them to stable kernels. > > > > > > Can you please do that here? > > > > Sure. Added to Cc list. > > They have no context here at all :( Let me post it again: Please consider applying d2155fe54ddb ("mm: compaction: remove duplicate !list_empty(&sublist) check") to 5.10 and 5.4, as it resolves a -Wdangling-pointer warning in recent GCC versions: In function '__list_cut_position', inlined from 'list_cut_position' at ./include/linux/list.h:400:3, inlined from 'move_freelist_tail' at mm/compaction.c:1241:3: ./include/linux/list.h:370:21: warning: storing the address of local variable 'sublist' in '*&freepage_6(D)->D.15621.D.15566.lru.next' [-Wdangling-pointer=] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Please apply d2155fe54ddb to 5.10 and 5.4 2025-04-22 6:34 ` Qingfang Deng @ 2025-04-22 7:04 ` David Hildenbrand 2025-04-22 9:58 ` Qingfang Deng 0 siblings, 1 reply; 8+ messages in thread From: David Hildenbrand @ 2025-04-22 7:04 UTC (permalink / raw) To: Qingfang Deng, Greg Kroah-Hartman Cc: Sasha Levin, stable, linux-mm, Zi Yan, Johannes Weiner, Brendan Jackman, Michal Hocko, Suren Baghdasaryan, Vlastimil Babka, Andrew Morton, Liu Xiang On 22.04.25 08:34, Qingfang Deng wrote: > On Tue, Apr 22, 2025 at 2:27 PM Greg Kroah-Hartman > <gregkh@linuxfoundation.org> wrote: >> On Tue, Apr 22, 2025 at 02:10:53PM +0800, Qingfang Deng wrote: >>> On Tue, Apr 22, 2025 at 2:06 PM Greg Kroah-Hartman >>> <gregkh@linuxfoundation.org> wrote: >>>> All mm patches MUST get approval from the mm maintainers/developers >>>> before we can apply them to stable kernels. >>>> >>>> Can you please do that here? >>> >>> Sure. Added to Cc list. >> >> They have no context here at all :( > > Let me post it again: > > Please consider applying d2155fe54ddb ("mm: compaction: remove > duplicate !list_empty(&sublist) check") to 5.10 and 5.4, as it > resolves a -Wdangling-pointer warning in recent GCC versions: > > In function '__list_cut_position', > inlined from 'list_cut_position' at ./include/linux/list.h:400:3, > inlined from 'move_freelist_tail' at mm/compaction.c:1241:3: > ./include/linux/list.h:370:21: warning: storing the address of local > variable 'sublist' in '*&freepage_6(D)->D.15621.D.15566.lru.next' > [-Wdangling-pointer=] The commit looks harmless. But I don't see how it could fix any warning? I mean, we replace two !list_empty() checks by a single one ... and the warning is about list_cut_position() ? -- Cheers, David / dhildenb ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Please apply d2155fe54ddb to 5.10 and 5.4 2025-04-22 7:04 ` David Hildenbrand @ 2025-04-22 9:58 ` Qingfang Deng 2025-04-22 12:41 ` Greg Kroah-Hartman 0 siblings, 1 reply; 8+ messages in thread From: Qingfang Deng @ 2025-04-22 9:58 UTC (permalink / raw) To: David Hildenbrand Cc: Greg Kroah-Hartman, Sasha Levin, stable, linux-mm, Zi Yan, Johannes Weiner, Brendan Jackman, Michal Hocko, Suren Baghdasaryan, Vlastimil Babka, Andrew Morton, Liu Xiang Hi David, On Tue, Apr 22, 2025 at 3:04 PM David Hildenbrand <david@redhat.com> wrote: > > Let me post it again: > > > > Please consider applying d2155fe54ddb ("mm: compaction: remove > > duplicate !list_empty(&sublist) check") to 5.10 and 5.4, as it > > resolves a -Wdangling-pointer warning in recent GCC versions: > > > > In function '__list_cut_position', > > inlined from 'list_cut_position' at ./include/linux/list.h:400:3, > > inlined from 'move_freelist_tail' at mm/compaction.c:1241:3: > > ./include/linux/list.h:370:21: warning: storing the address of local > > variable 'sublist' in '*&freepage_6(D)->D.15621.D.15566.lru.next' > > [-Wdangling-pointer=] > > The commit looks harmless. But I don't see how it could fix any warning? > > I mean, we replace two !list_empty() checks by a single one ... and the > warning is about list_cut_position() ? I have no idea, actually. Maybe the double !list_empty() confuses the compiler, making it think `sublist` can be referenced out of the scope? > > -- > Cheers, > > David / dhildenb > ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Please apply d2155fe54ddb to 5.10 and 5.4 2025-04-22 9:58 ` Qingfang Deng @ 2025-04-22 12:41 ` Greg Kroah-Hartman 2025-04-23 7:37 ` Qingfang Deng 0 siblings, 1 reply; 8+ messages in thread From: Greg Kroah-Hartman @ 2025-04-22 12:41 UTC (permalink / raw) To: Qingfang Deng Cc: David Hildenbrand, Sasha Levin, stable, linux-mm, Zi Yan, Johannes Weiner, Brendan Jackman, Michal Hocko, Suren Baghdasaryan, Vlastimil Babka, Andrew Morton, Liu Xiang On Tue, Apr 22, 2025 at 05:58:26PM +0800, Qingfang Deng wrote: > Hi David, > > > On Tue, Apr 22, 2025 at 3:04 PM David Hildenbrand <david@redhat.com> wrote: > > > Let me post it again: > > > > > > Please consider applying d2155fe54ddb ("mm: compaction: remove > > > duplicate !list_empty(&sublist) check") to 5.10 and 5.4, as it > > > resolves a -Wdangling-pointer warning in recent GCC versions: > > > > > > In function '__list_cut_position', > > > inlined from 'list_cut_position' at ./include/linux/list.h:400:3, > > > inlined from 'move_freelist_tail' at mm/compaction.c:1241:3: > > > ./include/linux/list.h:370:21: warning: storing the address of local > > > variable 'sublist' in '*&freepage_6(D)->D.15621.D.15566.lru.next' > > > [-Wdangling-pointer=] > > > > The commit looks harmless. But I don't see how it could fix any warning? > > > > I mean, we replace two !list_empty() checks by a single one ... and the > > warning is about list_cut_position() ? > > I have no idea, actually. Maybe the double !list_empty() confuses the > compiler, making it think `sublist` can be referenced out of the > scope? That is odd, are you sure this isn't a compiler bug? ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Please apply d2155fe54ddb to 5.10 and 5.4 2025-04-22 12:41 ` Greg Kroah-Hartman @ 2025-04-23 7:37 ` Qingfang Deng 2025-04-23 7:39 ` Greg Kroah-Hartman 0 siblings, 1 reply; 8+ messages in thread From: Qingfang Deng @ 2025-04-23 7:37 UTC (permalink / raw) To: Greg Kroah-Hartman Cc: David Hildenbrand, Sasha Levin, stable, linux-mm, Zi Yan, Johannes Weiner, Brendan Jackman, Michal Hocko, Suren Baghdasaryan, Vlastimil Babka, Andrew Morton, Liu Xiang On Tue, Apr 22, 2025 at 8:41 PM Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > > > > > > The commit looks harmless. But I don't see how it could fix any warning? > > > > > > I mean, we replace two !list_empty() checks by a single one ... and the > > > warning is about list_cut_position() ? > > > > I have no idea, actually. Maybe the double !list_empty() confuses the > > compiler, making it think `sublist` can be referenced out of the > > scope? > > That is odd, are you sure this isn't a compiler bug? I think it is a compiler bug. If so, what should we do to fix the warning? ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Please apply d2155fe54ddb to 5.10 and 5.4 2025-04-23 7:37 ` Qingfang Deng @ 2025-04-23 7:39 ` Greg Kroah-Hartman 0 siblings, 0 replies; 8+ messages in thread From: Greg Kroah-Hartman @ 2025-04-23 7:39 UTC (permalink / raw) To: Qingfang Deng Cc: David Hildenbrand, Sasha Levin, stable, linux-mm, Zi Yan, Johannes Weiner, Brendan Jackman, Michal Hocko, Suren Baghdasaryan, Vlastimil Babka, Andrew Morton, Liu Xiang On Wed, Apr 23, 2025 at 03:37:39PM +0800, Qingfang Deng wrote: > On Tue, Apr 22, 2025 at 8:41 PM Greg Kroah-Hartman > <gregkh@linuxfoundation.org> wrote: > > > > > > > > The commit looks harmless. But I don't see how it could fix any warning? > > > > > > > > I mean, we replace two !list_empty() checks by a single one ... and the > > > > warning is about list_cut_position() ? > > > > > > I have no idea, actually. Maybe the double !list_empty() confuses the > > > compiler, making it think `sublist` can be referenced out of the > > > scope? > > > > That is odd, are you sure this isn't a compiler bug? > > I think it is a compiler bug. If so, what should we do to fix the warning? Fix the compiler :) ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2025-04-23 7:40 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CALW65jbBY3EyRD-5vXz6w87Q+trxaod-QVy2NhVxLNcQHVw0hg@mail.gmail.com>
[not found] ` <2025042251-energize-preorder-31cd@gregkh>
2025-04-22 6:10 ` Please apply d2155fe54ddb to 5.10 and 5.4 Qingfang Deng
2025-04-22 6:27 ` Greg Kroah-Hartman
2025-04-22 6:34 ` Qingfang Deng
2025-04-22 7:04 ` David Hildenbrand
2025-04-22 9:58 ` Qingfang Deng
2025-04-22 12:41 ` Greg Kroah-Hartman
2025-04-23 7:37 ` Qingfang Deng
2025-04-23 7:39 ` Greg Kroah-Hartman
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox