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] [day] [month] [year] [list]
Message-ID: <CAKYAXd9MONk+mwHSXnoUTVVHqFytFPpfth1uvpcKx9q=g2yPWw@mail.gmail.com>
Date:	Mon, 21 Jan 2013 21:04:15 +0900
From:	Namjae Jeon <linkinjeon@...il.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	jaegeuk.kim@...sung.com,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-f2fs-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [patch] f2fs: use _safe() version of list_for_each

2013/1/21, Dan Carpenter <dan.carpenter@...cle.com>:
> I sometimes write little user space programs to help me check my
> work.  I've attached one.
>
> gcc test.c
> ./a.out
>
> regards,
> dan carpenter
>
Hi Dan.
Thanks for testcase. I understand fully.
list_for_each still use pos after removing pos in loop. So, we need to
use _safe function to get pos->next safely.

Thanks.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ