From: Nicolas Boichat <drinkcat@chromium.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
linux-fsdevel@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
Dave Chinner <dchinner@redhat.com>,
Luis Lozano <llozano@chromium.org>,
Ian Lance Taylor <iant@google.com>
Subject: Re: [BUG] copy_file_range with sysfs file as input
Date: Wed, 3 Feb 2021 17:18:19 +0800 [thread overview]
Message-ID: <CANMq1KAPe8F2WVsxYnP46Zx7K_0YSpnAUgod1WjenhOcHRk2kA@mail.gmail.com> (raw)
In-Reply-To: <YBpnBUD+QoMW9NtL@kroah.com>
On Wed, Feb 3, 2021 at 5:04 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Mon, Jan 25, 2021 at 03:54:31PM +0800, Nicolas Boichat wrote:
> > Hi copy_file_range experts,
> >
> > We hit this interesting issue when upgrading Go compiler from 1.13 to
> > 1.15 [1]. Basically we use Go's `io.Copy` to copy the content of
> > `/sys/kernel/debug/tracing/trace` to a temporary file.
>
> Nit, the above file is NOT a sysfs file. Odds are it is either a
> debugfs, or a tracefs file, please check your mounts to determine which
> it is, as that matters a lot on the kernel backend side for trying to
> figure out what is going on here :)
Yes yes it's tracefs ,-) But, from the other thread
https://lkml.org/lkml/2021/1/26/2029 sysfs (and any other fs that
generates files dynamically like procfs) would likely hit issues as
well (but maybe in more rare circumstances).
Thanks!
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2021-02-03 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 7:54 [BUG] copy_file_range with sysfs file as input Nicolas Boichat
2021-01-25 19:44 ` Ian Lance Taylor
2021-01-26 1:34 ` Dave Chinner
2021-01-26 3:50 ` Nicolas Boichat
2021-01-26 7:49 ` Dave Chinner
2021-02-03 9:04 ` Greg KH
2021-02-03 9:18 ` Nicolas Boichat [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=CANMq1KAPe8F2WVsxYnP46Zx7K_0YSpnAUgod1WjenhOcHRk2kA@mail.gmail.com \
--to=drinkcat@chromium.org \
--cc=amir73il@gmail.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=iant@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llozano@chromium.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).