Re: [PATCH 2/2] Fix i_state of inode is changed after the inode is freed [try #2]

Hi, Nathan

>Which doesn't look correct due to your need_iput guard, but perhaps
>we should do this instead...

I think that your fix is simpler, so I agree it.


Masayuki
-
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:
- Re: [PATCH 2/2] Fix i_state of inode is changed after the inode is freed [try #2]
  - From: Nathan Scott <[email protected]>

Prev by Date: Re: [PATCH 2/6] BC: beancounters core (API)
Next by Date: [RFC][PATCH 0/4] Redesign cpu_hotplug locking.
Previous by thread: Re: [PATCH 2/2] Fix i_state of inode is changed after the inode is freed [try #2]
Next by thread: Re: [PATCH 2/2] Fix i_state of inode is changed after the inode is freed [try #2]
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]