| 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
| ||
|
Message-ID: <544527A3.7030508@nod.at>
Date: Mon, 20 Oct 2014 17:17:55 +0200
From: Richard Weinberger <richard@....at>
To: dedekind1@...il.com
CC: linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] UBI: Fastmap: Care about the protection queue
Am 20.10.2014 um 16:46 schrieb Artem Bityutskiy:
> On Thu, 2014-10-16 at 12:06 +0200, Richard Weinberger wrote:
>> Am 14.10.2014 um 12:23 schrieb Artem Bityutskiy:
>>> On Mon, 2014-10-13 at 23:04 +0200, Richard Weinberger wrote:
>>>> Am 13.10.2014 um 17:23 schrieb Artem Bityutskiy:
>>>>> Well, used and free are RB-trees, looking them up is slow.
>>>>
>>>> This is true but we'd have to look it up in multiple trees and the protection queue...
>>>
>>> Right. 2 RB-trees, and one list. The list is empty most of the time, or
>>> contains one element.
>>
>> Actually it is the free, used and scrub tree plus the protection queue.
>
> OK, still does not change my point: 3 trees and a list which is mostly
> empty or short. Not that bad.
>
> Besides, the used tree is the large one, contains most of the stuff. The
> scrub tree is usually small, and mostly empty. The erroneous tree also
> mostly empty.
>
> So this in most of the cases, this will be about looking up a single
> tree.
>
> And again, all you need is:
>
> 1. all used
> 2. all scrub
> 3. all erroneous
Agreed.
>> Then there is another place where PEBs can hide, the erase work queue.
>
> That's just fastmap code not doing the right thing. We should not touch
> the work queue directly at all. What we _should_ do instead is to make
> it empty by asking the subsystem which manages it to flush it.
>
> 1. Lock the work queue to prevent anyone from submitting new jobs while
> we are in process of writing the fastmap.
> 2. Flush all works
> 3. do all the fastmap write stuff
> 4. Unlock
Are you sure? Flushing all works before every fastmap write will slow UBI down.
The fastmap write is not cheap. The goal should be to make it faster.
>> This brings me to an issue I've recently identified and fixed in my local queue.
>>
>> ubi_wl_put_peb() does the following:
>> if (in_wl_tree(e, &ubi->used)) {
>> self_check_in_wl_tree(ubi, e, &ubi->used);
>> rb_erase(&e->u.rb, &ubi->used);
>> } else if (in_wl_tree(e, &ubi->scrub)) {
>> self_check_in_wl_tree(ubi, e, &ubi->scrub);
>> rb_erase(&e->u.rb, &ubi->scrub);
>> } else if (in_wl_tree(e, &ubi->erroneous)) {
>> self_check_in_wl_tree(ubi, e, &ubi->erroneous);
>> rb_erase(&e->u.rb, &ubi->erroneous);
>> ubi->erroneous_peb_count -= 1;
>> ubi_assert(ubi->erroneous_peb_count >= 0);
>> /* Erroneous PEBs should be tortured */
>> torture = 1;
>> } else {
>> err = prot_queue_del(ubi, e->pnum);
>> if (err) {
>> ubi_err("PEB %d not found", pnum);
>> ubi_ro_mode(ubi);
>> spin_unlock(&ubi->wl_lock);
>> return err;
>> }
>> }
>> }
>> spin_unlock(&ubi->wl_lock);
>>
>> err = schedule_erase(ubi, e, vol_id, lnum, torture);
>>
>> If it happens that a fastmap write is needed between spin_unlock() and schedule_erase(), fastmap
>> will miss this PEB.
>
> You say is that LEBs change while you are writing fastmap. Of course
> they do. We should have a locking mechanism in place which would prevent
> this.
Not really. As fastmap will take the work semaphore no work is processed while
writing the fastmap. In this case the PEB is in flight between RB trees and the
work queue. Fastmap can miss it. But it won't change.
> Mat be wl_lock needs to become a mutex, or may be there should be
> separate mutex.
>
> Or may be 'ubi_wl_put_peb()' should go through the fatmap subsystem
> which should be able to block it if it is writing fastmap.
>
> Ideally, you should be able to "freeze" the state (of course for a short
> time), prepare fastmap data structures in memory, unfreeze, let users to
> further IO, and wirte fastmap.
Fastmap does this already. It takes various locks to freeze the state.
> This is roughly what UBIFS does when committing. It freezes all writers,
> builds the commit list, unfreezes the writers, and continues the commit
> process.
>
> Now, to be that advanced, you need a journal. Without journal, you do
> freeze, prepare and write, unfreeze. The end results is that writers are
> blocked for longer time, but this may be good enough.
I think we're becoming to scientific now.
>> What do you think?
>
> I think that UBI is memory consumption grows linearly with the flash
> growth. Mount time was linear too, fastmap is supposed to improve this.
With fastmap you have anyways a higher memory consumption.
To begin with the vmalloc()'ed ubi->fm_buf which holds the complete fastmap
in memory while reading/writing it.
> I know that there are people, who also reported their issues in this
> mailing list, who are very concerned about UBI memory consumption.
>
> And I think that fastmap should try really hard to not only improve the
> mount time, but also not to make the memory consumption problem worse.
>
> So yes, I understand code niceness argument. I really do. But this
> should not make UBI problem to be an even worse problem.
You can up with the niceness arguments, and now you're suddenly extremely
focusing on the memory footprint.
> Please, let's try much harder to go without increasing the memory
> footprint.
I need to go back to the drawing board. But first I have to fix/analyze
various bugs. Then I'll maybe have time again for memory/design nicefications.
Don't await any new patches for fastmap within the next weeks.
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists