From: Bart Van Assche <bvanassche@acm.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Bodo Stroesser <bostroesser@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Joel Becker <jlbec@evilplan.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [GIT PULL] configfs fix for Linux 5.14
Date: Sat, 14 Aug 2021 11:25:35 -0700 [thread overview]
Message-ID: <eca7f963-7ee1-d062-8020-a2a32a69a9e6@acm.org> (raw)
In-Reply-To: <CAHk-=whh8F-9Q=h=V=bKczqfRPbUN_A3h21aVfkk2HNhCWF+Pw@mail.gmail.com>
On 8/14/21 9:27 AM, Linus Torvalds wrote:
> On Fri, Aug 13, 2021 at 9:00 PM Christoph Hellwig <hch@infradead.org> wrote:
>>
>> configfs fix for Linux 5.14
>>
>> - fix to revert to the historic write behavior (Bart Van Assche)
>
> It would have been lovely to see what the problem was, but the commit
> doesn't actually explain that.
>
> I suspect it's this
>
> https://lkml.org/lkml/2021/7/26/581
>
> but there might have been more.
Hi Linus,
Bodo explained to me via a private email that the historic behavior is
the behavior he needs for a patch that he is still working on. I'm not
aware of any existing user space software that relies on the historic
(non-POSIX) behavior of configfs writes.
Bart.
next prev parent reply other threads:[~2021-08-14 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 6:59 Christoph Hellwig
2021-08-14 16:27 ` Linus Torvalds
2021-08-14 18:25 ` Bart Van Assche [this message]
2021-08-15 20:57 ` Bodo Stroesser
2021-08-14 16:38 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2021-07-14 16:33 Christoph Hellwig
2021-07-14 20:05 ` Linus Torvalds
2021-07-14 20:16 ` Linus Torvalds
2021-07-16 1:13 ` pr-tracker-bot
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=eca7f963-7ee1-d062-8020-a2a32a69a9e6@acm.org \
--to=bvanassche@acm.org \
--cc=bostroesser@gmail.com \
--cc=hch@infradead.org \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®