From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Al Viro <viro@zeniv.linux.org.uk>, <tytso@mit.edu>,
<adilger.kernel@dilger.ca>
Cc: <linux-ext4@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: [PATCH 2/2] ext4: Fix up the .write callback to use new_sync_write
Date: Wed, 23 Apr 2014 16:46:46 +0300 [thread overview]
Message-ID: <1398260806-19340-3-git-send-email-peter.ujfalusi@ti.com> (raw)
In-Reply-To: <1398260806-19340-1-git-send-email-peter.ujfalusi@ti.com>
Other filesystems has been updated but ext4 has been left out and since
ext4 does not provide aio_write callback we have kernel crash in
do_sync_write()
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
---
fs/ext4/file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/file.c b/fs/ext4/file.c
index f48a1c2838b6..708aad768199 100644
--- a/fs/ext4/file.c
+++ b/fs/ext4/file.c
@@ -587,7 +587,7 @@ loff_t ext4_llseek(struct file *file, loff_t offset, int whence)
const struct file_operations ext4_file_operations = {
.llseek = ext4_llseek,
.read = new_sync_read,
- .write = do_sync_write,
+ .write = new_sync_write,
.read_iter = generic_file_read_iter,
.write_iter = ext4_file_write_iter,
.unlocked_ioctl = ext4_ioctl,
--
1.9.2
prev parent reply other threads:[~2014-04-23 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 13:46 [PATCH 0/2] fs/ext4: fix for aio_write related kernel crash in linux-next Peter Ujfalusi
2014-04-23 13:46 ` [PATCH 1/2] fs: read_write: Check ->aio_write in __kernel_write() and vfs_write() Peter Ujfalusi
2014-04-23 13:46 ` Peter Ujfalusi [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=1398260806-19340-3-git-send-email-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).