From: P J P <ppandit@redhat.com>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Petr Matousek <pmatouse@redhat.com>
Subject: Re: [PATCH] To add NULL pointer check
Date: Wed, 3 Apr 2013 14:43:48 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.03.1304031342550.23577@erqung.pbz> (raw)
In-Reply-To: <1364975688.4353.7.camel@kjgkr>
+-- On Wed, 3 Apr 2013, Jaegeuk Kim wrote --+
| I'm confusing the question because f2fs doesn't use generic_writepages(),
| since f2fs_write_data_pages() is linked to a_ops->writepages. In
| do_writepages(), always f2fs_write_data_pages() is triggered instead of
| generic_writepages(). Isn't it?
Before commit fa9150a84c, when `generic_writepages' returned 0, it did not
abort `f2fs_write_data_pages', as the proposed patch does. I was wondering if
that's intentional OR if the patch below does it right?
===
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 7bd22a2..7be750e 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -561,7 +561,7 @@ static int f2fs_write_data_pages(struct address_space
*mapping,
{
struct inode *inode = mapping->host;
struct f2fs_sb_info *sbi = F2FS_SB(inode->i_sb);
- int ret;
+ int ret = 0;
long excess_nrtw = 0, desired_nrtw;
if (wbc->nr_to_write < MAX_DESIRED_PAGES_WP) {
@@ -572,7 +572,9 @@ static int f2fs_write_data_pages(struct address_space *mapping,
if (!S_ISDIR(inode->i_mode))
mutex_lock(&sbi->writepages);
- ret = write_cache_pages(mapping, wbc, __f2fs_writepage, mapping);
+ /* deal with chardevs and other special file */
+ if (mapping->a_ops->writepage)
+ ret = write_cache_pages(mapping, wbc, __f2fs_writepage, mapping);
if (!S_ISDIR(inode->i_mode))
mutex_unlock(&sbi->writepages);
f2fs_submit_bio(sbi, DATA, (wbc->sync_mode == WB_SYNC_ALL));
===
Thank you.
--
Prasad J Pandit / Red Hat Security Response Team
DB7A 84C5 D3F9 7CD1 B5EB C939 D048 7860 3655 602B
next prev parent reply other threads:[~2013-04-03 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 12:57 [PATCH] To add NULL pointer check P J P
2013-04-03 3:03 ` Jaegeuk Kim
2013-04-03 4:25 ` Namjae Jeon
2013-04-03 6:39 ` P J P
2013-04-03 7:00 ` P J P
2013-04-03 7:54 ` Jaegeuk Kim
2013-04-03 9:13 ` P J P [this message]
2013-04-04 0:14 ` Jaegeuk Kim
2013-04-04 5:28 ` P J P
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=alpine.LFD.2.03.1304031342550.23577@erqung.pbz \
--to=ppandit@redhat.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmatouse@redhat.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;
as well as URLs for NNTP newsgroup(s).