From: santosh.shilimkar@oracle.com (santosh.shilimkar@oralce.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] soc: ti: knav_qmss_queue: Use list_for_each_entry_safe to prevent use after free
Date: Mon, 03 Nov 2014 10:27:16 -0800 [thread overview]
Message-ID: <5457C904.8070203@oracle.com> (raw)
In-Reply-To: <1414819993.23500.1.camel@phoenix>
On 10/31/2014 10:33 PM, Axel Lin wrote:
> list_for_each_entry_safe() is necessary if list objects are deleted from
> the list while traversing it.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
Right. Picked up for 3.19. Thanks !!
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: "santosh.shilimkar@oralce.com" <santosh.shilimkar@oracle.com>
To: Axel Lin <axel.lin@ingics.com>, Santosh Shilimkar <ssantosh@kernel.org>
Cc: Sandeep Nair <sandeep_n@ti.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: ti: knav_qmss_queue: Use list_for_each_entry_safe to prevent use after free
Date: Mon, 03 Nov 2014 10:27:16 -0800 [thread overview]
Message-ID: <5457C904.8070203@oracle.com> (raw)
In-Reply-To: <1414819993.23500.1.camel@phoenix>
On 10/31/2014 10:33 PM, Axel Lin wrote:
> list_for_each_entry_safe() is necessary if list objects are deleted from
> the list while traversing it.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
Right. Picked up for 3.19. Thanks !!
Regards,
Santosh
next prev parent reply other threads:[~2014-11-03 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 5:33 [PATCH] soc: ti: knav_qmss_queue: Use list_for_each_entry_safe to prevent use after free Axel Lin
2014-11-01 5:33 ` Axel Lin
2014-11-03 18:27 ` santosh.shilimkar@oralce.com [this message]
2014-11-03 18:27 ` santosh.shilimkar@oralce.com
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=5457C904.8070203@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.