Re: Umount failing due to a file leak on 3.18 Android

2016-04-19 Thread Greg KH
On Tue, Apr 19, 2016 at 06:26:27PM -0700, Nikhilesh Reddy wrote: > Hi > > I am looking into a bug that results in umount failures ( since there is a > mount ref from the leaked file that is never freed on the mount ) > > The issue seems to be a result of the following callstack > >

Re: Umount failing due to a file leak on 3.18 Android

2016-04-19 Thread Greg KH
On Tue, Apr 19, 2016 at 06:26:27PM -0700, Nikhilesh Reddy wrote: > Hi > > I am looking into a bug that results in umount failures ( since there is a > mount ref from the leaked file that is never freed on the mount ) > > The issue seems to be a result of the following callstack > >

Re: Umount failing due to a file leak on 3.18 Android

2016-04-19 Thread Nikhilesh Reddy
Adding Arve Hjønnevåg and Riley Andrews I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call trace: 39.958108:

Re: Umount failing due to a file leak on 3.18 Android

2016-04-19 Thread Nikhilesh Reddy
Adding Arve Hjønnevåg and Riley Andrews I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call trace: 39.958108:

Re: Umount failing due to a file leak on 3.18 Android

2016-04-19 Thread Nikhilesh Reddy
On Tue 19 Apr 2016 06:26:27 PM PDT, Nikhilesh Reddy wrote: Hi I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call

Re: Umount failing due to a file leak on 3.18 Android

2016-04-19 Thread Nikhilesh Reddy
On Tue 19 Apr 2016 06:26:27 PM PDT, Nikhilesh Reddy wrote: Hi I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call

Umount failing due to a file leak on 3.18 Android

2016-04-19 Thread Nikhilesh Reddy
Hi I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call trace: 39.958108: <2> [] fput+0x1e0/0x1f8 39.958113:

Umount failing due to a file leak on 3.18 Android

2016-04-19 Thread Nikhilesh Reddy
Hi I am looking into a bug that results in umount failures ( since there is a mount ref from the leaked file that is never freed on the mount ) The issue seems to be a result of the following callstack 39.958104: <6> Call trace: 39.958108: <2> [] fput+0x1e0/0x1f8 39.958113: