From: Salvatore Mesoraca <s.mesoraca16@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [bug report] namei: allow restricted O_CREAT of FIFOs and regular files
Date: Thu, 26 Apr 2018 19:28:01 +0200 [thread overview]
Message-ID: <CAJHCu1LUQeOzcXOBq+-vPgU4+2pSX19QZ_Njry9n3Ma_+TQ07w@mail.gmail.com> (raw)
In-Reply-To: <20180426081456.GA7060@mwanda>
2018-04-26 10:14 GMT+02:00 Dan Carpenter <dan.carpenter@oracle.com>:
> Hello Salvatore Mesoraca,
>
> The patch 0d70abf05029: "namei: allow restricted O_CREAT of FIFOs and
> regular files" from Apr 23, 2018, leads to the following static
> checker warning:
>
> fs/namei.c:3390 do_last()
> error: uninitialized symbol 'inode'.
Thank you very much for this report.
I'll address this issue in the next version.
Salvatore
prev parent reply other threads:[~2018-04-26 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 8:14 [bug report] namei: allow restricted O_CREAT of FIFOs and regular files Dan Carpenter
2018-04-26 17:28 ` Salvatore Mesoraca [this message]
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=CAJHCu1LUQeOzcXOBq+-vPgU4+2pSX19QZ_Njry9n3Ma_+TQ07w@mail.gmail.com \
--to=s.mesoraca16@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-fsdevel@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).