diff options
| author |   Bob Peterson <rpeterso@redhat.com> | 2020-04-29 08:45:54 -0500 |
|---|---|---|
| committer |   Andreas Gruenbacher <agruenba@redhat.com> | 2020-06-02 19:45:05 +0200 |
| commit | ea22eee4e6027d8927099de344f7fff43c507ef9 (patch) | |
| tree | 6a95d8c0d8a3e7ba4bc6909502dade31cf79ff59 /fs/gfs2 | |
| parent | gfs2: Don't ignore inode write errors during inode_go_sync (diff) | |
| download | wireguard-linux-ea22eee4e6027d8927099de344f7fff43c507ef9.tar.xz wireguard-linux-ea22eee4e6027d8927099de344f7fff43c507ef9.zip | |
gfs2: Allow lock_nolock mount to specify jid=X
Before this patch, a simple typo accidentally added \n to the jid=
string for lock_nolock mounts. This made it impossible to mount a
gfs2 file system with a journal other than journal0. Thus:
mount -tgfs2 -o hostdata="jid=1" <device> <mount pt>
Resulted in:
mount: wrong fs type, bad option, bad superblock on <device>
In most cases this is not a problem. However, for debugging and
testing purposes we sometimes want to test the integrity of other
journals. This patch removes the unnecessary \n and thus allows
lock_nolock users to specify an alternate journal.
Signed-off-by: Bob Peterson <rpeterso@redhat.com>
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Diffstat (limited to 'fs/gfs2')
| -rw-r--r-- | fs/gfs2/ops_fstype.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c index e2b69ffcc6a8..094f5fe7c009 100644 --- a/fs/gfs2/ops_fstype.c +++ b/fs/gfs2/ops_fstype.c @@ -880,7 +880,7 @@ fail: } static const match_table_t nolock_tokens = { - { Opt_jid, "jid=%d\n", }, + { Opt_jid, "jid=%d", }, { Opt_err, NULL }, }; |