From: Frank Mori Hess <fmh6jj@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: jffs2: stack dump on sync
Date: Wed, 8 Nov 2017 19:07:14 -0500 [thread overview]
Message-ID: <CAJz5OpfT79Fu0-bTKxcuMBXp140xUF1pp0kS0Q=F90DeUqN5RA@mail.gmail.com> (raw)
Hi, I'm using kernel 4.1.17 and I noticed jffs2 dumping stacktraces on
sync, as reported here:
https://patchwork.ozlabs.org/patch/298933/#689224
As far as I can tell, this has not been fixed in newer versions
although I haven't tested them. It seems the problem occurs when
CONFIG_JFFS2_FS_WRITEBUFFER is enabled, which causes jffs2_sync_fs()
in jffs2/super.c to call
cancel_delayed_work_sync(&c->wbuf_dwork);
However, wbuf_dwork is generally not initialized, producing the stack dump.
--
Frank
reply other threads:[~2017-11-09 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJz5OpfT79Fu0-bTKxcuMBXp140xUF1pp0kS0Q=F90DeUqN5RA@mail.gmail.com' \
--to=fmh6jj@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.