From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 65701] oops: fs/ext4/ext4_jbd2.c
Date: Mon, 25 Nov 2013 09:38:07 +0000 [thread overview]
Message-ID: <bug-65701-13602-10RNyYX6A2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65701-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=65701
Dmitry Monakhov <dmonakhov@openvz.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmonakhov@openvz.org
--- Comment #1 from Dmitry Monakhov <dmonakhov@openvz.org> ---
In fact this is not ext4's issue, this is generic fs issue.
pipe_write() do not accuire sb_start_write(), as far as I understand this is
because pipe should not touch fs's data. But it is not completely correct
because pipe want update file's time. Let's use same trick as we use in
touch_time()
pipe_write will call sb_start_write_try() and skip time update on frozen fs.
See proposed patch.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-11-25 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 23:44 [Bug 65701] New: oops: fs/ext4/ext4_jbd2.c bugzilla-daemon
2013-11-25 9:38 ` bugzilla-daemon [this message]
2013-11-25 9:39 ` [Bug 65701] " bugzilla-daemon
2013-11-25 22:15 ` bugzilla-daemon
2013-11-26 8:07 ` bugzilla-daemon
2013-11-26 21:30 ` bugzilla-daemon
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=bug-65701-13602-10RNyYX6A2@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).