From: Jan Kara <jack@suse.cz>
To: Tao Ma <tm@tao.ma>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ext3: Remove the obsolete broken EXT3_IOC32_WAIT_FOR_READONLY.
Date: Sat, 8 Oct 2011 00:12:33 +0200 [thread overview]
Message-ID: <20111007221233.GD30754@quack.suse.cz> (raw)
In-Reply-To: <1318000878-2928-1-git-send-email-tm@tao.ma>
On Fri 07-10-11 23:21:18, Tao Ma wrote:
> From: Tao Ma <boyu.mt@taobao.com>
>
> There are no user of EXT3_IOC32_WAIT_FOR_READONLY and also it is
> broken. No one set the set_ro_timer, no one wake up us and our
> state is set to TASK_INTERRUPTIBLE not RUNNING. So remove it.
Hmm, I vaguely recall Andrew had some debugging patches which were using
turn_ro_timer and this functionality. But I'm not sure if they are still
usable or if they still make sense when one can easily test crashing using
virtual machines... Andrew?
Honza
>
> Cc: Jan Kara <jack@suse.cz>
> Signed-off-by: Tao Ma <boyu.mt@taobao.com>
> ---
> fs/ext3/ioctl.c | 24 ------------------------
> include/linux/ext3_fs_sb.h | 4 ----
> 2 files changed, 0 insertions(+), 28 deletions(-)
>
> diff --git a/fs/ext3/ioctl.c b/fs/ext3/ioctl.c
> index c7f4394..ba1b54e 100644
> --- a/fs/ext3/ioctl.c
> +++ b/fs/ext3/ioctl.c
> @@ -150,30 +150,6 @@ setversion_out:
> mnt_drop_write(filp->f_path.mnt);
> return err;
> }
> -#ifdef CONFIG_JBD_DEBUG
> - case EXT3_IOC_WAIT_FOR_READONLY:
> - /*
> - * This is racy - by the time we're woken up and running,
> - * the superblock could be released. And the module could
> - * have been unloaded. So sue me.
> - *
> - * Returns 1 if it slept, else zero.
> - */
> - {
> - struct super_block *sb = inode->i_sb;
> - DECLARE_WAITQUEUE(wait, current);
> - int ret = 0;
> -
> - set_current_state(TASK_INTERRUPTIBLE);
> - add_wait_queue(&EXT3_SB(sb)->ro_wait_queue, &wait);
> - if (timer_pending(&EXT3_SB(sb)->turn_ro_timer)) {
> - schedule();
> - ret = 1;
> - }
> - remove_wait_queue(&EXT3_SB(sb)->ro_wait_queue, &wait);
> - return ret;
> - }
> -#endif
> case EXT3_IOC_GETRSVSZ:
> if (test_opt(inode->i_sb, RESERVATION)
> && S_ISREG(inode->i_mode)
> diff --git a/include/linux/ext3_fs_sb.h b/include/linux/ext3_fs_sb.h
> index 258088a..6436525 100644
> --- a/include/linux/ext3_fs_sb.h
> +++ b/include/linux/ext3_fs_sb.h
> @@ -76,10 +76,6 @@ struct ext3_sb_info {
> struct mutex s_resize_lock;
> unsigned long s_commit_interval;
> struct block_device *journal_bdev;
> -#ifdef CONFIG_JBD_DEBUG
> - struct timer_list turn_ro_timer; /* For turning read-only (crash simulation) */
> - wait_queue_head_t ro_wait_queue; /* For people waiting for the fs to go read-only */
> -#endif
> #ifdef CONFIG_QUOTA
> char *s_qf_names[MAXQUOTAS]; /* Names of quota files with journalled quota */
> int s_jquota_fmt; /* Format of quota to use */
> --
> 1.7.1
>
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2011-10-07 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 15:21 [PATCH] ext3: Remove the obsolete broken EXT3_IOC32_WAIT_FOR_READONLY Tao Ma
2011-10-07 22:12 ` Jan Kara [this message]
2011-10-08 20:52 ` Ted Ts'o
2011-10-10 16:27 ` Jan Kara
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=20111007221233.GD30754@quack.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tm@tao.ma \
/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