From: Andrew Morton <akpm@linux-foundation.org>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Richard Weinberger <richard@nod.at>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 0 PID: 913 at fs/inode.c:275 drop_nlink+0x4b/0x50()
Date: Mon, 14 Dec 2015 14:19:04 -0800 [thread overview]
Message-ID: <20151214141904.f5e083536008e900bf48646c@linux-foundation.org> (raw)
In-Reply-To: <566DEEF3.9090504@oracle.com>
On Sun, 13 Dec 2015 23:19:31 +0100 Vegard Nossum <vegard.nossum@oracle.com> wrote:
> On 11/26/2015 09:30 AM, OGAWA Hirofumi wrote:
> > Vegard Nossum <vegard.nossum@oracle.com> writes:
> >> On 11/25/2015 10:54 PM, OGAWA Hirofumi wrote:
> >>> Vegard Nossum <vegard.nossum@oracle.com> writes:
> >>>> On 11/23/2015 11:21 PM, Richard Weinberger wrote:
> >>>>> Am 23.11.2015 um 08:55 schrieb Vegard Nossum:
> >>>>>> With the attached vfat disk image (fuzzed), I get the
> >>>>>> following WARNING:
> >>>>>>
> >>>>>> WARNING: CPU: 0 PID: 913 at fs/inode.c:275
> >>>>>> drop_nlink+0x4b/0x50()
> >> [...]
> >>> Can you try this one?
> >> That seems to fix the problem here, thanks!
> > Andrew, please queue this up for next chance.
>
> Sorry to bug you, I didn't see this merged yet and just making sure this
> doesn't slip through the cracks. Or should I expect it only for the next
> merge window?
I merged this into -mm on Nov 11. I'd assumed it was 4.5 material. Was
that wrong?
prev parent reply other threads:[~2015-12-14 22:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 7:55 Vegard Nossum
2015-11-23 22:21 ` Richard Weinberger
2015-11-24 8:08 ` Vegard Nossum
2015-11-25 21:54 ` OGAWA Hirofumi
2015-11-26 8:12 ` Vegard Nossum
2015-11-26 8:26 ` OGAWA Hirofumi
2015-11-26 8:30 ` OGAWA Hirofumi
2015-12-13 22:19 ` Vegard Nossum
2015-12-14 22:19 ` Andrew Morton [this message]
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=20151214141904.f5e083536008e900bf48646c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=vegard.nossum@oracle.com \
/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®