Re: [PATCH] exec: do not leave bprm->interp on stack

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Kees Cook <keescook@xxxxxxxxxxxx>
Subject: Re: [PATCH] exec: do not leave bprm->interp on stack
From: P J P <ppandit@xxxxxxxxxx>
Date: Mon, 26 Nov 2012 11:53:00 +0530 (IST)
Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx>, jjlinux-kernel@xxxxxxxxxxxxxxx, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Josh Triplett <josh@xxxxxxxxxxxxxxxx>, Serge Hallyn <serge.hallyn@xxxxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, halfdog <me@xxxxxxxxxxx>
In-reply-to: <CAGXu5jL8zCt5ghW4ODPL9+SyC9+mbuw=4JMUngepY5fC8pSikQ@mail.gmail.com>

+-- On Sat, 24 Nov 2012, Kees Cook wrote --+
| Well, "ever" meaning "if depth is hit, always fail out", yes. This is 
| intentional. We do not want to attempt module loading if we hit a recursion 
| limit.

  Ah yes, that's right!

Thanks so much! :)
--
Prasad J Pandit / Red Hat Security Response Team
DB7A 84C5 D3F9 7CD1 B5EB  C939 D048 7860 3655 602B
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

References:
- [PATCH] exec: do not leave bprm->interp on stack
  - From: Kees Cook
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: P J P
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: Kees Cook
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: P J P
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: Kees Cook
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: P J P
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: Kees Cook
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: P J P
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: Kees Cook
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: P J P
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: Kees Cook
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: P J P
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: Kees Cook
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: P J P
- Re: [PATCH] exec: do not leave bprm->interp on stack
  - From: Kees Cook

Prev by Date: Re: [PATCH, 3.7-rc7, RESEND] fs: revert commit bbdd6808 to fallocate UAPI
Next by Date: Re: [PATCH 1/2] autofs4: allow autofs to work outside the initial PID namespace
Previous by thread: Re: [PATCH] exec: do not leave bprm->interp on stack
Next by thread: Re: [PATCH] exec: do not leave bprm->interp on stack
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]