From: Edward Shishkin <edward.shishkin@gmail.com>
To: ReiserFS development mailing list <reiserfs-devel@vger.kernel.org>
Subject: [PATCH 2/3] reiser4: fixup status writes
Date: Sun, 16 Aug 2015 15:22:42 +0200 [thread overview]
Message-ID: <55D08EA2.5050902@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: reiser4-fixup-status_write.patch --]
[-- Type: text/x-patch, Size: 590 bytes --]
Reset bio in reiser4_status_write() to prevent oops in error paths.
Signed-off-by: Edward Shishkin <edward.shishkin@gmail.com>
---
fs/reiser4/status_flags.c | 1 +
1 file changed, 1 insertion(+)
--- a/fs/reiser4/status_flags.c
+++ b/fs/reiser4/status_flags.c
@@ -145,6 +145,7 @@ int reiser4_status_write(__u64 status, _
strncpy(statuspage->texterror, message, REISER4_TEXTERROR_LEN);
kunmap_atomic((char *)statuspage);
+ bio_reset(bio);
bio->bi_bdev = sb->s_bdev;
bio->bi_io_vec[0].bv_page = get_super_private(sb)->status_page;
bio->bi_io_vec[0].bv_len = sb->s_blocksize;
next reply other threads:[~2015-08-16 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 13:22 Edward Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-16 18:15 [PATCH 2/3] reiser4: fixup status writes Edward Shishkin
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=55D08EA2.5050902@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=reiserfs-devel@vger.kernel.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).