linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang JieJing <kzjeef@gmail.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] ubifs: add update vfs super block infomation when remount to ro mode
Date: Thu, 29 Apr 2010 10:14:29 +0800	[thread overview]
Message-ID: <i2rcf7b913c1004281914kbe0c0c18xeee2e1bbcc375012@mail.gmail.com> (raw)
In-Reply-To: <1272439453.7750.20.camel@localhost>

(resend since HTML mail rejected by linux-fsdevel.)
Hi Artem,

I just clone the  git://git.infradead.org/ubifs-2.6.git, and git am my
patch, It is very clean patched, so, maybe your git repo code is very
new, so the patch can't cleaned apply.

This is my first patch give back to upstream, even I read the kernel
document 'how-to send patch' but still something leaked.
If I did something wrong, Please show me the right way or something like that,
Thanks for your time.

---
Best regards,
Zhang Jiejing



2010/4/28 Artem Bityutskiy <dedekind1@gmail.com>:
> On Fri, 2010-04-16 at 11:36 +0800, ZhangJieJing wrote:
>> If some read/write error happens(eg.CRC error), ubifs make self a read
>> only mode,
>> but the vfs infomation still not update.
>> This patch add this also make /proc/mounts update.
>>
>> Signed-off-by: Zhang Jiejing <kzjeef@gmail.com>
>> ---
>>  fs/ubifs/io.c |    1 +
>>  1 files changed, 1 insertions(+), 0 deletions(-)
>> diff --git a/fs/ubifs/io.c b/fs/ubifs/io.c
>> index 0168271..d33c233 100644
>> --- a/fs/ubifs/io.c
>> +++ b/fs/ubifs/io.c
>> @@ -63,6 +63,7 @@ void ubifs_ro_mode(struct ubifs_info *c, int err)
>>        if (!c->ro_media) {
>>                c->ro_media = 1;
>>                c->no_chk_data_crc = 0;
>> +              c->vfs_sb->s_flags |= MS_RDONLY;
>>                ubifs_warn("switched to read-only mode, error %d", err);
>>                dbg_dump_stack();
>>        }
>> --
>> 1.6.3.3
>
> Your patch is not applicable. Try to save your own e-mail and apply the
> patch with 'git am'.
>
> Applying: UBIFS: mark VFS SB RO too
> fatal: corrupt patch at line 9
> Patch failed at 0001 UBIFS: mark VFS SB RO too
> When you have resolved this problem run "git am -i --resolved".
> If you would prefer to skip this patch, instead run "git am -i --skip".
> To restore the original branch and stop patching run "git am -i
> --abort".
> [dedekind@sauron ubifs-2.6]\$ patch -p1 < .git/rebase-apply/patch
> patching file fs/ubifs/io.c
> patch: **** malformed patch at line 9: �� � � if (!c->ro_media) {
>
>
> But I've fixed this up and applied manually. It is now in the
> ubifs-2.6.git tree, thanks.
>
> --
> Best Regards,
> Artem Bityutskiy (Артём Битюцкий)
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-04-29  2:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16  3:36 [PATCH] ubifs: add update vfs super block infomation when remount to ro mode ZhangJieJing
2010-04-16 19:10 ` Artem Bityutskiy
2010-04-28  7:24 ` Artem Bityutskiy
2010-04-29  2:14   ` Zhang JieJing [this message]
2010-04-29  3:46     ` Artem Bityutskiy
2010-04-29  6:36       ` Zhang JieJing
2010-04-29  6:44         ` Artem Bityutskiy
2010-04-29  6:38       ` Zhang JieJing

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=i2rcf7b913c1004281914kbe0c0c18xeee2e1bbcc375012@mail.gmail.com \
    --to=kzjeef@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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).