Re: [patch 1/1] selinux: do not clear f_op when removing entries

On Wed, 21 Nov 2007, Stephen Smalley wrote:

> Do not clear f_op when removing entries since it isn't safe to do.
> 
> Signed-off-by:  Stephen Smalley <[email protected]>

Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/selinux-2.6.git#for-akpm


-- 
James Morris
<[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 1/4] proc: fix NULL ->i_fop oops
  - From: Alexey Dobriyan <[email protected]>
- Re: [PATCH 1/4] proc: fix NULL ->i_fop oops
  - From: Christoph Hellwig <[email protected]>
- Re: [PATCH 1/4] proc: fix NULL ->i_fop oops
  - From: Stephen Smalley <[email protected]>
- Re: [PATCH 1/4] proc: fix NULL ->i_fop oops
  - From: Christoph Hellwig <[email protected]>
- [patch 1/1] selinux: do not clear f_op when removing entries
  - From: Stephen Smalley <[email protected]>

Prev by Date: Possible bug from kernel 2.6.22 and above
Next by Date: Re: 2.6.24-rc3-mm1: I/O error, system hangs
Previous by thread: Re: [patch 1/1] selinux: do not clear f_op when removing entries
Next by thread: [PATCH 2/4] proc: detect duplicate names on registration
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]