From: NeilBrown <neilb@suse.com>
To: Oleg Drokin <oleg.drokin@intel.com>, Al Viro <viro@ZenIV.linux.org.uk>
Cc: Greg Kroah-Hartman <greg@kroah.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH 03/12] staging: lustre: llite: fix various issues with ll_splice_alias.
Date: Wed, 19 Jul 2017 14:33:33 +1000 [thread overview]
Message-ID: <87o9shxcyq.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <030281CD-CC74-429C-910F-86706CFC57DA@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Tue, Jul 18 2017, Oleg Drokin wrote:
> Unfortunately this patch causes insta-crash on first stat call after mount.
> Sorry, I cannot dig into this deeper right this moment, but I will a bit later.
V.strange. The crash suggests that the lock, and hence the inode, is
not initialized. I cannot see how that might happen.
though...
>> + spin_lock(&lli->lli_lock);
>> + new = ll_find_invalid_alias(inode, de);
>> + if (!new)
>> + d_add(de, inode);
>> + spin_lock(&lli->lli_lock);
Had it not crashed, it would have deadlocked. That second spin_lock()
should be spin_unlock() :-( I don't *think* that would have caused this crash...
> I am adding Al that we discussed this code at some length and he found no problems
> here, so I am a bit surprised by your findings.
I'd be very happy to read Al's thoughts.
> Also the reason we reinvent the d_splice_alias is because we need to
> splice not just directories, but also regular files.
I see that. A key simplification I bring is that directories and
non-directories can be handled separately. d_splice_alias() does
all we need for directories, and nothing useful for non-dirs.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-07-19 4:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 23:26 [PATCH 00/12] Assorted lustre fixes and improvements NeilBrown
2017-07-18 23:26 ` [PATCH 06/12] staging: lustre: ldlm: remove unneeded 'err' arg to ldlm_process_flock_lock() NeilBrown
2017-07-18 23:26 ` [PATCH 11/12] staging: lustre: ldlm: remove unnecessary 'ownlocks' variable NeilBrown
2017-07-18 23:26 ` [PATCH 12/12] staging: lustre: ldlm: remove unused field 'fwd_generation' NeilBrown
2017-07-18 23:26 ` [PATCH 05/12] staging: lustre: ldlm: remove unused 'work_list' arg from ldlm_process_flock_lock() NeilBrown
2017-07-18 23:26 ` [PATCH 02/12] staging: lustre: llite: fix incorrect DCACHE_DISCONNECTED test NeilBrown
2017-07-18 23:26 ` [PATCH 01/12] staging: lustre: fix minor typos in comments NeilBrown
2017-07-19 8:29 ` Greg KH
2017-08-02 3:26 ` [PATCH] " NeilBrown
2017-08-03 17:29 ` [lustre-devel] " James Simmons
2017-07-18 23:26 ` [PATCH 07/12] staging: lustre: ldlm: remove 'flags' arg from ldlm_process_flock_lock() NeilBrown
2017-07-18 23:26 ` [PATCH 09/12] staging: lustre: ldlm: remove 'flags' arg from ldlm_flock_destroy() NeilBrown
2017-07-18 23:26 ` [PATCH 08/12] staging: lustre: ldlm: remove unused 'overlaps' variable NeilBrown
2017-07-18 23:26 ` [PATCH 10/12] staging: lustre: ldlm: tidy list walking in ldlm_flock() NeilBrown
[not found] ` <BN6PR1101MB2132359E48C9904D3E305EE7CBA60@BN6PR1101MB2132.namprd11.prod.outlook.com>
2017-07-19 4:36 ` [lustre-devel] " NeilBrown
2017-07-18 23:26 ` [PATCH 03/12] staging: lustre: llite: fix various issues with ll_splice_alias NeilBrown
2017-07-19 2:51 ` Oleg Drokin
2017-07-19 4:33 ` NeilBrown [this message]
2017-07-19 6:18 ` Oleg Drokin
2017-07-18 23:26 ` [PATCH 04/12] staging: lustre: ldlm: remove 'first_enq' arg from ldlm_process_flock_lock() NeilBrown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9shxcyq.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=andreas.dilger@intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®