linux-kernel - Re: [PATCHv5 00/15] kill unnecessary bdi wakeups + cleanups

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: <1280048478.9990.3.camel@localhost>
Date:	Sun, 25 Jul 2010 12:01:18 +0300
From:	Artem Bityutskiy <dedekind1@...il.com>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCHv5 00/15] kill unnecessary bdi wakeups + cleanups

On Sun, 2010-07-25 at 11:29 +0300, Artem Bityutskiy wrote:
> Changes since v4
> Most patches are intact. Only patches N9, N10 and N14 were changed. And patch
> N15 was added. Also, now I tested the patch-set much better.
> 
> 1. Fix a bug found while testing: in the forker thread, when we create a bdi
>    task and then assign it to 'bdi->wb.task', we need to take the
>    'bdi->work_lock'. Otherwise we can lose a wake-up. Changed this in patch
>    N10.
> 2. Add patch 15 which fixes a warning and cleans up 'bdi_register()'.
> 3. Use "switch" in the main forker thread loop. Patch N9 was changed and now it
>    also introduces the "switch".
> 4. Stick with Christoph's version of tracepoint names and positions -> changed
>    patch N14.
> 5. Add a couple of "Reviewed-by" tags.

Oh, completely forgot to mention another thing.

6. Addressed the issue pointed to by Christoph and added
  'del_timer_sync()'

So patch N12 was also tweaked.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

--
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/