RE: [PATCH] pstore: Solve lockdep warning by moving inode locks

.kernel.org; > Anton Vorontsov <an...@enomsg.org>; Colin Cross <ccr...@android.com>; > Luck, Tony <tony.l...@intel.com>; Namhyung Kim <namhy...@kernel.org> > Subject: Re: [PATCH] pstore: Solve lockdep warning by moving inode locks > > On Fri, Apr 28

RE: [PATCH] pstore: Solve lockdep warning by moving inode locks

uck, Tony ; Namhyung Kim > Subject: Re: [PATCH] pstore: Solve lockdep warning by moving inode locks > > On Fri, Apr 28, 2017 at 2:00 AM, Lofstedt, Marta > wrote: > > > > > >> -Original Message- > >> From: Chris Wilson [mailto:ch...@chris-wilson.co.uk] >

Re: [PATCH] pstore: Solve lockdep warning by moving inode locks

>> Cc: linux-kernel@vger.kernel.org; Anton Vorontsov <an...@enomsg.org>; >> Colin Cross <ccr...@android.com>; Luck, Tony <tony.l...@intel.com>; >> Lofstedt, Marta <marta.lofst...@intel.com>; Namhyung Kim >> <namhy...@kernel.org> >> Subjec

Re: [PATCH] pstore: Solve lockdep warning by moving inode locks

ontsov ; >> Colin Cross ; Luck, Tony ; >> Lofstedt, Marta ; Namhyung Kim >> >> Subject: Re: [PATCH] pstore: Solve lockdep warning by moving inode locks >> >> On Thu, Apr 27, 2017 at 04:20:37PM -0700, Kees Cook wrote: >> > Lockdep complains about a possible dea

RE: [PATCH] pstore: Solve lockdep warning by moving inode locks

@android.com>; Luck, Tony <tony.l...@intel.com>; > Lofstedt, Marta <marta.lofst...@intel.com>; Namhyung Kim > <namhy...@kernel.org> > Subject: Re: [PATCH] pstore: Solve lockdep warning by moving inode locks > > On Thu, Apr 27, 2017 at 04:20:37PM -0700, Kees Cook

RE: [PATCH] pstore: Solve lockdep warning by moving inode locks

: Re: [PATCH] pstore: Solve lockdep warning by moving inode locks > > On Thu, Apr 27, 2017 at 04:20:37PM -0700, Kees Cook wrote: > > Lockdep complains about a possible deadlock between mount and unlink > > (which is technically impossible), but fixing this improves possible &

Re: [PATCH] pstore: Solve lockdep warning by moving inode locks

On Thu, Apr 27, 2017 at 04:20:37PM -0700, Kees Cook wrote: > Lockdep complains about a possible deadlock between mount and unlink > (which is technically impossible), but fixing this improves possible > future multiple-backend support, and keeps locking in the right order. I have merged your

Re: [PATCH] pstore: Solve lockdep warning by moving inode locks

On Thu, Apr 27, 2017 at 04:20:37PM -0700, Kees Cook wrote: > Lockdep complains about a possible deadlock between mount and unlink > (which is technically impossible), but fixing this improves possible > future multiple-backend support, and keeps locking in the right order. I have merged your

Re: [PATCH] pstore: Solve lockdep warning by moving inode locks

Hi, On Fri, Apr 28, 2017 at 8:20 AM, Kees Cook wrote: > Lockdep complains about a possible deadlock between mount and unlink > (which is technically impossible), but fixing this improves possible > future multiple-backend support, and keeps locking in the right order. > >

Re: [PATCH] pstore: Solve lockdep warning by moving inode locks

Hi, On Fri, Apr 28, 2017 at 8:20 AM, Kees Cook wrote: > Lockdep complains about a possible deadlock between mount and unlink > (which is technically impossible), but fixing this improves possible > future multiple-backend support, and keeps locking in the right order. > > The lockdep warning

[PATCH] pstore: Solve lockdep warning by moving inode locks

Lockdep complains about a possible deadlock between mount and unlink (which is technically impossible), but fixing this improves possible future multiple-backend support, and keeps locking in the right order. The lockdep warning could be triggered by unlinking a file in the pstore filesystem:

[PATCH] pstore: Solve lockdep warning by moving inode locks

Lockdep complains about a possible deadlock between mount and unlink (which is technically impossible), but fixing this improves possible future multiple-backend support, and keeps locking in the right order. The lockdep warning could be triggered by unlinking a file in the pstore filesystem: