From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Sam Li <faithilikerun@gmail.com>,
qemu-devel@nongnu.org, stefanha@redhat.com,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>
Cc: dlemoal@kernel.org, dmitry.fomichev@wdc.com, hare@suse.de,
qemu-block@nongnu.org
Subject: Re: [PATCH 1/2] block/file-posix: fix g_file_get_contents return path
Date: Thu, 27 Jul 2023 07:46:46 -0400 [thread overview]
Message-ID: <648eecec-3035-22a5-3040-cd9906534d29@linux.ibm.com> (raw)
In-Reply-To: <96628b6b-a9e9-c817-7d2a-211bb47f5eb5@linux.ibm.com>
On 7/5/23 10:54 AM, Matthew Rosato wrote:
> On 6/4/23 2:16 AM, Sam Li wrote:
>> The g_file_get_contents() function returns a g_boolean. If it fails, the
>> returned value will be 0 instead of -1. Solve the issue by skipping
>> assigning ret value.
>>
>> This issue was found by Matthew Rosato using virtio-blk-{pci,ccw} backed
>> by an NVMe partition e.g. /dev/nvme0n1p1 on s390x.
>>
>> Signed-off-by: Sam Li <faithilikerun@gmail.com>
>
> Polite ping on this patch -- this issue still exists in master as of today and this patch resolves it for me. Just want to make sure it gets into 8.1
>
Ping -- I can still reproduce this crash on -rc1. Any chance this patch can get picked up for the 8.1 release?
@Sam I see you sent a v2 of only patch #2 in this series ('block/file-posix: fix wps checking in raw_co_prw').. I wonder if this one just got forgotten since it wasn't sent as part of v2. Maybe try a resend of this patch by itself (plus the review tags added)?
Thanks,
Matt
>
>> ---
>> block/file-posix.c | 6 ++----
>> 1 file changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/block/file-posix.c b/block/file-posix.c
>> index ac1ed54811..0d9d179a35 100644
>> --- a/block/file-posix.c
>> +++ b/block/file-posix.c
>> @@ -1232,7 +1232,6 @@ static int hdev_get_max_hw_transfer(int fd, struct stat *st)
>> static int get_sysfs_str_val(struct stat *st, const char *attribute,
>> char **val) {
>> g_autofree char *sysfspath = NULL;
>> - int ret;
>> size_t len;
>>
>> if (!S_ISBLK(st->st_mode)) {
>> @@ -1242,8 +1241,7 @@ static int get_sysfs_str_val(struct stat *st, const char *attribute,
>> sysfspath = g_strdup_printf("/sys/dev/block/%u:%u/queue/%s",
>> major(st->st_rdev), minor(st->st_rdev),
>> attribute);
>> - ret = g_file_get_contents(sysfspath, val, &len, NULL);
>> - if (ret == -1) {
>> + if (!g_file_get_contents(sysfspath, val, &len, NULL)) {
>> return -ENOENT;
>> }
>>
>> @@ -1253,7 +1251,7 @@ static int get_sysfs_str_val(struct stat *st, const char *attribute,
>> if (*(p + len - 1) == '\n') {
>> *(p + len - 1) = '\0';
>> }
>> - return ret;
>> + return 0;
>> }
>> #endif
>>
>
>
next prev parent reply other threads:[~2023-07-27 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 6:16 [PATCH 1/2] block/file-posix: fix g_file_get_contents return path Sam Li
2023-06-04 6:16 ` [PATCH 2/2] block/file-posix: fix wps checking in raw_co_prw Sam Li
2023-06-07 16:08 ` Stefan Hajnoczi
2023-06-07 13:51 ` [PATCH 1/2] block/file-posix: fix g_file_get_contents return path Matthew Rosato
2023-06-07 16:04 ` Stefan Hajnoczi
2023-07-05 14:54 ` Matthew Rosato
2023-07-27 11:46 ` Matthew Rosato [this message]
2023-07-27 11:51 ` Sam Li
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=648eecec-3035-22a5-3040-cd9906534d29@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=dlemoal@kernel.org \
--cc=dmitry.fomichev@wdc.com \
--cc=faithilikerun@gmail.com \
--cc=hare@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).