From: ebiederm@xmission.com (Eric W. Biederman)
To: Philipp Hahn <hahn@univention.de>
Cc: linux-fsdevel@vger.kernel.org,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Felix Botner <botner@univention.de>,
Dirk Wiesenthal <wiesenthal@univention.de>
Subject: Re: OOPS: linux-4.9.33/fs/pnode.c:propagate_one()
Date: Tue, 03 Oct 2017 11:48:10 -0500 [thread overview]
Message-ID: <87lgksb2k5.fsf@xmission.com> (raw)
In-Reply-To: <8760c2u5bh.fsf@xmission.com> (Eric W. Biederman's message of "Thu, 28 Sep 2017 12:00:02 -0500")
ebiederm@xmission.com (Eric W. Biederman) writes:
> Philipp Hahn <hahn@univention.de> writes:
>
>> We will try 4.9.52 next and see, if we can still reproduce it.
Can you still reproduce this on 4.9.52?
I am not seeing anything obvious that would result in last_source
becomming NULL there so knowing I am not lookning for a phantom would be very
helpful.
Eric
next prev parent reply other threads:[~2017-10-03 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 13:03 OOPS: linux-4.9.33/fs/pnode.c:propagate_one() Philipp Hahn
2017-09-28 17:00 ` Eric W. Biederman
2017-10-03 16:48 ` Eric W. Biederman [this message]
2017-10-04 13:18 ` Philipp Hahn
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=87lgksb2k5.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=botner@univention.de \
--cc=hahn@univention.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wiesenthal@univention.de \
/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