linux-kernel - Re: [QUESTION] llist: Comment releasing 'must delete' restriction before traversing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87d0v4mbgx.fsf@yhuang-dev.intel.com>
Date:   Tue, 31 Jul 2018 09:37:50 +0800
From:   "Huang\, Ying" <ying.huang@...el.com>
To:     Byungchul Park <byungchul.park@....com>
Cc:     <linux-kernel@...r.kernel.org>, <kernel-team@....com>,
        <peterz@...radead.org>, <mingo@...nel.org>,
        <jiangshanlai@...il.com>, <paulmck@...ux.vnet.ibm.com>,
        <josh@...htriplett.org>, <rostedt@...dmis.org>,
        <mathieu.desnoyers@...icios.com>, <joel@...lfernandes.org>,
        <len.brown@...el.com>, <glider@...gle.com>,
        <peter@...leysoftware.com>, <aik@...abs.ru>
Subject: Re: [QUESTION] llist: Comment releasing 'must delete' restriction before traversing

Byungchul Park <byungchul.park@....com> writes:

> Hello folks,
>
> I'm careful in saying.. and curious about..
>
> In restrictive cases like only addtions happen but never deletion, can't
> we safely traverse a llist? I believe llist can be more useful if we can
> release the restriction. Can't we?
>
> If yes, we may add another function traversing starting from a head. Or
> just use existing funtion with head->first.
>
> Thank a lot for your answers in advance :)

What's the use case?  I don't know how it is useful that items are never
deleted from the llist.

Some other locks could be used to provide mutual exclusive between

- llist add, llist traverse

and

- llist delete

Is this your use case?

Best Regards,
Huang, Ying