On Apr 08, Kees Cook wrote:
> On Tue, Apr 8, 2014 at 7:43 AM, Artem Bityutskiy
> wrote:
> > On Tue, 2014-04-08 at 10:57 -0300, Ezequiel Garcia wrote:
> >> Hello Kees,
> >>
> >> Thanks for the patch.
> >>
> >> On Apr 07, Kees Cook wrote:
> >> > When building the name for the workqueue thread, make
On Tue, Apr 8, 2014 at 7:43 AM, Artem Bityutskiy
wrote:
> On Tue, 2014-04-08 at 10:57 -0300, Ezequiel Garcia wrote:
>> Hello Kees,
>>
>> Thanks for the patch.
>>
>> On Apr 07, Kees Cook wrote:
>> > When building the name for the workqueue thread, make sure a format
>> > string cannot leak in from
On Tue, 2014-04-08 at 10:57 -0300, Ezequiel Garcia wrote:
> Hello Kees,
>
> Thanks for the patch.
>
> On Apr 07, Kees Cook wrote:
> > When building the name for the workqueue thread, make sure a format
> > string cannot leak in from the disk name.
> >
>
> Could you enlighten me and explain why
On Mon, 2014-04-07 at 21:44 -0700, Kees Cook wrote:
> When building the name for the workqueue thread, make sure a format
> string cannot leak in from the disk name.
>
> Signed-off-by: Kees Cook
Pushed to linux-ubifs / master, thanks!
--
Best Regards,
Artem Bityutskiy
--
To unsubscribe from
Hello Kees,
Thanks for the patch.
On Apr 07, Kees Cook wrote:
> When building the name for the workqueue thread, make sure a format
> string cannot leak in from the disk name.
>
Could you enlighten me and explain why you want to avoid the name leak?
Is it a security concern?
I'd like to
Hello Kees,
Thanks for the patch.
On Apr 07, Kees Cook wrote:
When building the name for the workqueue thread, make sure a format
string cannot leak in from the disk name.
Could you enlighten me and explain why you want to avoid the name leak?
Is it a security concern?
I'd like to
On Mon, 2014-04-07 at 21:44 -0700, Kees Cook wrote:
When building the name for the workqueue thread, make sure a format
string cannot leak in from the disk name.
Signed-off-by: Kees Cook keesc...@chromium.org
Pushed to linux-ubifs / master, thanks!
--
Best Regards,
Artem Bityutskiy
--
To
On Tue, 2014-04-08 at 10:57 -0300, Ezequiel Garcia wrote:
Hello Kees,
Thanks for the patch.
On Apr 07, Kees Cook wrote:
When building the name for the workqueue thread, make sure a format
string cannot leak in from the disk name.
Could you enlighten me and explain why you want to
On Tue, Apr 8, 2014 at 7:43 AM, Artem Bityutskiy
artem.bityuts...@linux.intel.com wrote:
On Tue, 2014-04-08 at 10:57 -0300, Ezequiel Garcia wrote:
Hello Kees,
Thanks for the patch.
On Apr 07, Kees Cook wrote:
When building the name for the workqueue thread, make sure a format
string
On Apr 08, Kees Cook wrote:
On Tue, Apr 8, 2014 at 7:43 AM, Artem Bityutskiy
artem.bityuts...@linux.intel.com wrote:
On Tue, 2014-04-08 at 10:57 -0300, Ezequiel Garcia wrote:
Hello Kees,
Thanks for the patch.
On Apr 07, Kees Cook wrote:
When building the name for the workqueue
When building the name for the workqueue thread, make sure a format
string cannot leak in from the disk name.
Signed-off-by: Kees Cook
---
drivers/mtd/ubi/block.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/ubi/block.c b/drivers/mtd/ubi/block.c
index
When building the name for the workqueue thread, make sure a format
string cannot leak in from the disk name.
Signed-off-by: Kees Cook keesc...@chromium.org
---
drivers/mtd/ubi/block.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/ubi/block.c
12 matches
Mail list logo
