From: Imran Khan <imran.f.khan@oracle.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
tj@kernel.org, gregkh@linuxfoundation.org,
viro@zeniv.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/4] kernfs: Change kernfs_notify_list to llist.
Date: Sat, 2 Jul 2022 01:06:03 +1000 [thread overview]
Message-ID: <ab856471-99f5-b70a-cf4e-5293a7d52957@oracle.com> (raw)
In-Reply-To: <ad06d3c3-7878-9106-e118-f89e2de91a1f@samsung.com>
Hello,
On 1/7/22 10:49 pm, Marek Szyprowski wrote:
> Hi,
>
> On 01.07.2022 14:20, Imran Khan wrote:
>> On 1/7/22 9:22 pm, Marek Szyprowski wrote:
>>> On 15.06.2022 04:10, Imran Khan wrote:
>>>> At present kernfs_notify_list is implemented as a singly linked
>>>> list of kernfs_node(s), where last element points to itself and
>>>> value of ->attr.next tells if node is present on the list or not.
>>>> Both addition and deletion to list happen under kernfs_notify_lock.
>>>>
>>>> Change kernfs_notify_list to llist so that addition to list can heppen
>>>> locklessly.
>>>>
>>>> Suggested by: Al Viro <viro@zeniv.linux.org.uk>
>>>> Signed-off-by: Imran Khan <imran.f.khan@oracle.com>
>>>> Acked-by: Tejun Heo <tj@kernel.org>
>>> This patch landed in linux next-20220630 as commit b8f35fa1188b
>>> ("kernfs: Change kernfs_notify_list to llist."). Unfortunately, it
>>> causes serious regression on my test systems. It can be easily noticed
>>> in the logs by the following warning:
>>>
[...]
>
> Yes, this fixes the issue. Feel free to add:
>
> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
>
> Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
>
Thanks a lot for testing. Sure I have added these tags. I have
send the patch for review at [1].
> Maybe it is related to the fact, that I have earlycon enabled on those
> machines?
>
For sure it is occuring with some tweaking in console settings. So far both the
reported occurences have this thing in common. I will be able to confirm further
if I could reproduce this locally and I am trying that at the moment.
I will share when I have some more findings.
Thanks
-- Imran
[1]: https://lore.kernel.org/lkml/20220701145047.2206900-1-imran.f.khan@oracle.com/
next prev parent reply other threads:[~2022-07-01 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 2:10 [PATCH v7 0/4] kernfs: make ->attr.open RCU protected Imran Khan
2022-06-15 2:10 ` [PATCH v7 1/4] " Imran Khan
2022-06-15 6:12 ` Tejun Heo
2022-06-15 2:10 ` [PATCH v7 2/4] kernfs: Change kernfs_notify_list to llist Imran Khan
2022-07-01 11:22 ` Marek Szyprowski
2022-07-01 12:20 ` Imran Khan
2022-07-01 12:49 ` Marek Szyprowski
2022-07-01 15:06 ` Imran Khan [this message]
2022-07-05 15:18 ` Geert Uytterhoeven
2022-06-15 2:10 ` [PATCH v7 3/4] kernfs: Introduce interface to access global kernfs_open_file_mutex Imran Khan
2022-06-15 2:10 ` [PATCH v7 4/4] kernfs: Replace global kernfs_open_file_mutex with hashed mutexes Imran Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab856471-99f5-b70a-cf4e-5293a7d52957@oracle.com \
--to=imran.f.khan@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox